docs: publish architectural decision records

[irinaschubert]

Issue Number: DEV-

Pull Request Checklist

Basic Requirements

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix: represents bug fixes
• Refactor: represents production code refactoring
• Feature: represents a new feature
• Documentation: documentation changes (no production code change)
• Chore: maintenance tasks (no production code change)
• Style: styles updates (no production code change)
• Test: all about tests: adding, refactoring tests (no production code change)
• Other... Please describe:

Does this PR introduce a breaking change?

• Yes
• No

Does this PR change client-test-data?

• Yes (don't forget to update the JS-LIB team about the change)
• No

Other information

It was decided that ADRs should be published on our official documentation website.

[codecov]

Codecov Report

Base: 86.95% // Head: 86.95% // No change to project coverage 👍

Coverage data is based on head (6f8eb98) compared to base (bfe578a).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2301   +/-   ##
=======================================
  Coverage   86.95%   86.95%           
=======================================
  Files         242      242           
  Lines       28102    28102           
=======================================
  Hits        24435    24435           
  Misses       3667     3667           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[BalduinLandolt]

LGTM. Not much of value to add from my side.
(There is of course much to improve in the docs, but that would be out of scope for this task.)

But it's impossible for me to keep track of all the links that have changed. Did you run the docs locally and click around to see if stuff still works?

[irinaschubert]

LGTM. Not much of value to add from my side. (There is of course much to improve in the docs, but that would be out of scope for this task.)

But it's impossible for me to keep track of all the links that have changed. Did you run the docs locally and click around to see if stuff still works?

@BalduinLandolt Thanks for your feedback! It's really hard to stop improving it, once you started... So, yes, there could be done much more to improve these docs!
I did run it locally and clicked around. mkdocs shows warnings if internal links are not working or if there are files not referenced in the nav file. I solved all these warnings, so I hope it is fine.