Restructure Remote Service doc for Java to include Service Binding based services

[StefanHenke]

This is a first draft of the structure for review. Does not yet contain all content.

The idea is to get some initial feedback on the new structure.

Preview build: https://capire-binding-based-remote-service.cfapps.sap.hana.ondemand.com/docs/java/cqn-services/remote-services

[beckermarc]

This is the default behaviour already, no explicit configuration is required for this (except the destination dependency in SaaS). Maybe we should rather turn the logic around and describe how to disable this, by setting the right retrieval strategy.

[StefanHenke]

I have adapted it again. It now does not feel as a variant anymore. But anyhow, after thinking again about the s4 scenario, I think this is actually always required to call into the subscriber tenant. Defining a destination to a s4 system in the provider account feels strange. S4 systems are not multi-tenant aware and, hence, are always dedicated for a specific customer with customer-specific credentials.

[github-actions]

Spelling Mistakes

• ./java/cqn-services/remote-services.md:117:21 Unknown word "Configuratiion"
• ./java/cqn-services/remote-services.md:135:189 Unknown word "xsuua"

Generally, for each spelling mistake there are 2 ways to fix it:

1. Fix the spelling mistake and commit it.
2. The word is incorrectly reported as misspelled → put the word on the project-words.txt list, located in the root project directory.

[github-actions]

Spelling Mistakes

• ./java/cqn-services/remote-services.md:137:189 Unknown word "xsuua"

Generally, for each spelling mistake there are 2 ways to fix it:

1. Fix the spelling mistake and commit it.
2. The word is incorrectly reported as misspelled → put the word on the project-words.txt list, located in the root project directory.

[github-actions]

Spelling Mistakes

• ./java/cqn-services/remote-services.md:120:4 Unknown word "constrast"

Generally, for each spelling mistake there are 2 ways to fix it:

1. Fix the spelling mistake and commit it.
2. The word is incorrectly reported as misspelled → put the word on the project-words.txt list, located in the root project directory.

[beckermarc]

code only is slightly misleading here now. I think we should make clear that this also works via configuration now (maybe simply <Y/> and link to our docs).

[StefanHenke]

Done. I have linked to our new binding-based approach. I guess this should be the preferred way over programmatically registering destinations

[beckermarc]

I think this guide needs to be adapted overall. It still deprecated property structures in a lot of areas, due to our latest changes. Also we should at least mention somewhere that in Java the new binding-based destinations are available (see also concerns below)

[StefanHenke]

I adapted all configurations. The whole guide focuses a lot on destinations, I was not aware of that guide before. Not sure if we need to adapt the guide on a second step to describe the binding-based approach more prominently.