[FEAT] Support extensibility of wadm manifest for configuration of external platforms

[brooksmtownsend]

For projects like the https://github.com/wasmCloud/wasmcloud-operator, it's critical to be able to specify additional fields in a wadm manifest in order to configure external infrastructure resources, like an endpoint in Kubernetes. It would be great for wadm to have additional support for metadata like annotations/labels that can be attached to components or links that will be stored (and ignored by wadm) but usable by tools administering wadm.

There are likely many ways to do this within the OAM specification and we should continue to reuse that standard.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!

[brooksmtownsend]

wasmCloud/wasmcloud-operator#46 should be viewed as an extension of this issue

[brooksmtownsend]

#306 provided a really nice way for us to tackle this in the wadm manifest, so calling this complete!