Upgrade tooling to 1.2.0

[MaximilianSoerenPollak]

Tooling 1.2.0 has been released and fixes a bug in docs-as-code & process (requirements collision => venv could not be created)

[github-actions]

The created documentation from the pull request is available at: docu-html

[MaximilianSoerenPollak]

@masc2023 Give me a second.

There seems to be an issue with tests not passing. I'm a bit confused why there even is a 'test' target in this repo, as there is no additional source code to be tested.
Is this not something that might be a leftover can be removed?

[masc2023]

@masc2023 Give me a second.

There seems to be an issue with tests not passing. I'm a bit confused why there even is a 'test' target in this repo, as there is no additional source code to be tested. Is this not something that might be a leftover can be removed?

There should be no source code to be tested, may required from integration/release team?

[MaximilianSoerenPollak]

@masc2023 Give me a second.
There seems to be an issue with tests not passing. I'm a bit confused why there even is a 'test' target in this repo, as there is no additional source code to be tested. Is this not something that might be a leftover can be removed?

There should be no source code to be tested, may required from integration/release team?

I have deleted the workflow that executes tests. It was me (way back when) who added it. I'm guessing it was a leftover from when the architecture was different.
I also took the liberty to upgrade bazel to 8.4.2 as ref-int has this as the version.
We already upgraded docs-as-code to that version too. Locally I did not see any change in behaviour.