Implement new "default" publisher

[davidfowl]

Description

• This publisher walks the model and tries to publish the resource if there's a specific annotation.
• Added supporting APIs for adding a publisher callback (mimics) the manifest publisher.
• Don't register publishers for k8s and docker compose anymore, just make those environment resources add publishing annotations.
• DockerComposeEnvironmentResource and KuberentesEnvironmentResource can publish
• GetDeploymentTarget can return the right target for the annotation

Contributes to #9089

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

[mitchdenny]

I like where this is going. Lets get it merged.