[EPIC] External-Name Compliance

[enrico-kaack-comp]

Context

In the second round of external-name discussion, we saw the neccessity to formaly define our external-name handling in the ADR.

Now we have to apply this decision to all our managed resources.

In the btp provder we already layed out the foundation we can now use in this provider too, like in this Epic.

Steps

1. bring the documentation generation over. The documentation should be written right at the API documentation in the types go files. see btp implementation for reference
2. For all resources:

• Ensure compliance according to the external name
• create import tests. Btp already has an import_tester that can be used (https://github.com/SAP/crossplane-provider-btp/blob/main/test/e2e/import_utils_test.go)
• create upgrade tests. Upgrade tests are already handled in [FEATURE] 6 Add Upgrade Tests for New Resources (OrgQuota, Route, Domain, App) #169. These are the base upgrade tests that should run every version. If the external name requires version migration, we run a custom upgrade test for this specific version.

Resources

• App
• Domain
• Org
• OrgMembers
• OrgQuota
• OrgRole
• Route
• ServiceCredentialBinding
• ServiceInstance
• ServiceRouteBinding
• Space
• SpaceMembers
• SpaceQuota
• SpaceRole

There is a subissue for every resource. Every issue is build the same.