[KOGITO-9838] Add a troubleshooting guide for remote service invocations

[ricardozanini]

JIRA:
https://issues.redhat.com/browse/KOGITO-9838

Description:
In this PR, we complement the work in KOGITO-9838 by adding a quick troubleshooting guide for remote service invocations. We should keep updating this guide with more information.

apache/incubator-kie-kogito-runtimes#3238

Please make sure that your PR meets the following requirements:

• You have read the contributions doc
• Pull Request title is properly formatted: KOGITO-XYZ Subject
• Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
• The nav.adoc file has a link to this guide in the proper category
• The index.adoc file has a card to this guide in the proper category, with a meaningful description

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

[fjtirado]

@ricardozanini
I think having a troubleshooting guide is a must (so really good idea) and the content you write in no time is really good, but I would add a longer introduction and convert the current in just one section, "hhtp troubleshooting", so current sections become sub-sections of that one.
That way, in the future, we can add more sections, for example GRPC troubleshooting or JQ troubleshooting.
wdyt?

[MarianMacik]

Looks good, just minor suggestions.

[ricardozanini]

@fjtirado can you take a look?

[MarianMacik]

Looks good now, thanks!