Export app profiles in publish metadata

[wolfy-j]

Summary

• add module manifest runtime profile publish policy (publish.profiles.enabled and publish.profiles.source)
• export all root app profiles from .wippy.yaml or the configured profile source into .wapp runtime.profiles metadata during publish
• reject public wippy.yaml metadata.runtime.profiles definitions so profile definitions have one canonical source
• reject split profile vars between the profile source and wippy.yaml metadata, and keep profile selection as a run/test-time concern
• ignore dependency pack profiles when loading multi-pack runtime defaults so profiles remain app-scoped

Semantics

Publishing does not choose or bake a profile. It uploads all app profiles from the configured profile source as artifact metadata. Consumers still select one later with wippy run --profile <name> / wippy test --profile <name>, layered below local .wippy.yaml and CLI overrides.

Tests

• go test -count=1 ./boot/deps/config ./cmd/wippy/cmd
• ./test.sh
• go test -count=1 ./...