Merge latest release notes with CLI and Sample repo info

[artemkovalyov]

What Has Changed?

Convert release notes into slightly more logical structure

Manual Checks?

• Text adheres to the style guide (vale docs/)
  • Every sentence is on its own line
  • Headings use title capitalization (applies also to the sidebar and title of a document)
  • You followed naming center guidelines when referring to SAP products (e.g. SAP S/4HANA)
• You checked your spelling and grammar (consider using Grammarly, see CONTRIBUTING.md)
• You formatted all changed files with prettier (npm run prettier)
• You tested if the documentation still builds (npm run build)
• You verified all new and changed links still work (changing the id or name of a file can break links)
• You have updated the feature matrix if you add documentation on a new feature or otherwise required.

[jjtang1985]

Thanks for taking care.
I feel merging the release notes might lead to confusing to the users and to us.
If the vale issue cannot be solved, I would even vote for deleting them from the release notes and keep them in some other pages if we need.

[jjtang1985]

I feel a bit confusing, as the the sample repo is not related to the new patch release.

[jjtang1985]

Also here, the cli repository and the npm package has nothing to do with the patch release.

[jjtang1985]

Please check #644, @artemkovalyov .

[artemkovalyov]

Here's my thinking @jjtang1985, SDK is a product as a whole. Samples repo or CLI don't have any value separately. That's why I look at the release of the core module as on a train to communicate other updates related to the development with the SDK.

Semantically, you are right but for customers having samples repo, CLI that is no longer developed is even more confusing.
I think we can restructure things by simply having a release date and collecting together everything that made it out by that date or around it. No customer would care about when we published the samples repo or deprecated the CLI 99.99% of the time.

What would you prefer as an approach? Would you be confused really or is it just your assumption the customers will be confused?
This is also a reason why having only a trace log of releases on the GH repo doesn't work any longer.