docs: ADR sdk package release + docs generation in MD

[curtis-h]

Description

This PR is adding ADR template and our first ADR to change the release process, contents are detailed in the DRAFT ADR.
Together with this ADR, we are removing the HTML documentation portal generation and deployment to github pages.
Instead, this PR will merge the docs into docs/sdk on each release.

The documentation portal will then grab this auto-generated md files and deploy them to the main website when needed.

Changes:

• Creating folder for holding ADRs
• first ADR considering how we release the SDK.
• Generate docs in docs/sdk with md files.
• Releasing a new version of docs on each release + commit using semantic release.

ADR - open for comment

Jira link

https://input-output.atlassian.net/browse/ATL-6147

Checklist

• Self-reviewed the diff
• New code has inline documentation
• New code has proper comments/tests
• Any changes not covered by tests have been tested manually

[github-actions]

Lines	Statements	Branches	Functions
	60.3% (1200/1990)	48.62% (512/1053)	62.36% (353/566)

JUnit

Tests	Skipped	Failures	Errors	Time
326	2 💤	0 ❌	0 🔥	37.581s ⏱️

[elribonazo]

@antonbaliasnikov @amagyar-iohk Hello fam, please check this ADR for better handling release candidates.

It drafts the different posibilities we have and the preferred choice which I checked against semantic-release configuration.

The ADR can be approved when considered, but i'd say we are really intereated on all the benefits it brings, lets try to do it the earliest possible to start the year properly!

[amagyar-iohk]

@elribonazo @curtis-h overall it looks good. I have only few questions

From what I understood, we'll have master and rc channels (+ maintenance ones)
During the development everything will be merged to master (except changes in maintenance channels) and when we want to test/prepare for a release, we merge from master to rc?
And if it is good, we release from the master branch?

[elribonazo]

From what I understood, we'll have master and rc channels (+ maintenance ones)
During the development everything will be merged to master (except changes in maintenance channels) and when we want to test/prepare for a release, we merge from master to rc?
And if it is good, we release from the master branch?

A commit in maintenance or RC branches will create RC or Beta packages, once those changes are ready, we will merge the changes from RC branches to master and when this happens a production release will happen and the package will be published to master.

So not really, we don't be pushing everything to master. All goes into the rc branches instead and you move from there to master when we have a production release and not an RC. Still deployment is manual, no issues there.

[elribonazo]

@amagyar-iohk more things have slightly changed here. The documentation side is being integrated in the main Atala docs website.

The Action to generate docs is removed from push + tags, we rely on semantic-release package to push the documentation changes on each release we make. This will integrate very nicely with what we are aiming to have, RC branches, etc.

Docs simply generate on each release no matter which one, thats all.
Needed on this PR, until its approved + merged the following PR is blocked: hyperledger/identus-docs#70

[amagyar-iohk]

thanks for the clarifications