BXMSDOC-6638: Update case docs for 7.9

[sterobin]

@krisv @gmunozfe @michelehaglund , ready for your review on the three case docs. See doc previews below. I updated outdated screenshots and nav instructions in the three case docs, based on the latest UI for 7.9, and also made various other improvements/tweaks/corrections along the way to these three docs and to other docs that contained the same issues. No other changes.

I replied to you in Jira that the following BAPLs. These were initially linked for these case docs, but actually do not have doc impact for reasons I explain in the Jira. Though @fjtirado might need to update the KIE Server REST API swagger source accordingly, as I explained in the Jira.

• https://issues.redhat.com/browse/BAPL-1623: Case tracability (no doc impact)
• https://issues.redhat.com/browse/BAPL-1575: Include case file details in API response (no doc impact)

Related links:

• Jira (basis for this PR, incorporates the other two docs too)
• Designing and building cases
• Getting started with case mgmt
• Using the Showcase app

[sterobin]

jenkins retest this please

[sterobin]

jenkins retest

[michelehaglund]

Changes look great. Thank you for catching the same issues throughout other docs @sterobin

[sterobin]

ok to test

[gmunozfe]

Looks good to me, well done @sterobin !

[krisv]

Is there an easy way to check the rendered output @sterobin ? The use of a slash at the beginning of a URL seems to be inconsistent, so wanted to maybe check the difference in the output?

[sterobin]

@krisv Fixed all, including the step about adding a case project, per our convo in chat. Also, regarding the backslashes, the rendered links are listed above for you to see. The inconsistency is intentional. The backslsash stops the URL from rendering as a clickable/active link. So where I don't want it to be clickable, backslash. Where I've it would be helpful for the user to just click and go, no backslash. This is something we're trying to standardize a bit in our docs for improved usability.