Feat: Support publishing to Business Accelerator Hub (api.sap.com)

[Fannon]

For Business Accelerator Hub (BAH) publishing, we need to split the ORD Packages from one package (current behavior) into one package per ORD resource type. Most notably this means that we need a dedicated package for assigning APIs and another one for the events.

[swennemers]

It should be there, also as default. But let's do a test run with our ORA sample apps once moved to the plugin.

[swennemers]

well... the code looks differently

[Fannon]

@aramovic79 The rules which are most important are here: https://pages.github.tools.sap/CentralEngineering/open-resource-discovery-specification/spec-extensions/policy-levels/sap-core-v1#package

If you validate with sap:core:v1 some problems should already pointed out. I hope it's mostly about splitting up packages up correctly, according to the constraints.

Example: You have one package, containing APIs, Events and Consumption Bundles.

Now you need to split it up into 3 Packages, containing only the same kind.
If you have mixed visibility, you again need to split up. So it could be 6 packages in the end.

E.g. MyPackage -> MyPackageAPIs, MyPackageEvents, MyPackageConsumptionBundles

Now with visibility: MyPackageAPIsInternal, MyPackageEventsInternal, MyPackageConsumptionBundlesInternal.

I would just append "Internal" and treat "public" as the default.