Add OSGi metadata to AWS CDK Java libraries

### Describe the feature

Add OSGi metadata to the aws-cdk Java artefacts, so it can be deployed and consumed in OSGi applications.

### Use Case

I want to create services that use the AWS CDK to be able to orchestrate applications in the cloud. I want to use OSGi, so the services can also be integrated in an Eclipse based application. This is currently not possible by using the artefacts published at Maven Central, as all artefacts doesn't contain the necessary OSGi metadata.

The only way I could verify that it is generally working, was to create wrapped bundles that consume the artefacts and add the OSGi metadata. But this is more a workaround for verification than a reliable solution.

### Proposed Solution

Add the [bnd-maven-plugin](https://github.com/bndtools/bnd/tree/master/maven-plugins/bnd-maven-plugin) or [Grade Plugins](https://github.com/bndtools/bnd/tree/master/gradle-plugins) to the build process of the AWS CDK Java libraries (dependent on whether Maven or Gradle is used), to get the OSGi metadata automatically generated at build time.

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.73

### Environment details (OS name and version, etc.)

Windows 10, Eclipse, Java 11

Start by tracing how the AWS CDK Java artefacts are built and published to Maven Central. Determine whether the build uses Maven or Gradle, then review the proposed bnd-maven-plugin or Bnd Gradle Plugins. Done means the published Java artefacts contain the required OSGi metadata and can be consumed by an OSGi application.

Written by the indexing model from the issue text.