Migrate build to version catalogs

[JL0000]

What is it?

• [ ] Bugfix (user facing)
• [ ] Feature (user facing)
• [x] Codebase improvement (dev facing)
• [x] Meta improvement to the project (dev facing)

Description of the changes in your PR

• Moved project dependencies from build files to a version catalog file.

Fixes the following issue(s)

• Fixes #10927

APK testing

The APK can be found by going to the "Checks" tab below the title. On the left pane, click on "CI", scroll down to "artifacts" and click "app" to download the zip file which contains the debug APK of this PR. You can find more info and a video demonstration on this wiki page.

Due diligence

• [x] I read the contribution guidelines.

[Stypox]

Thanks for the PR! This should go to the refactor branch though, as the dev branch is kind of in maintenance mode. You can change the base branch by clicking "Edit" next to the PR title.

[Profpatsch]

Okay, so I checked this out, squashed the last 3 commits into one, and I have to say I’m not particularly in favor of this.

Before, we had a pretty simple file with dependencies and their version numbers, now we have yet another toml file, and that file has yet another indirection, so we are introducing two indirections here for very little gain.

I’m in favor of closing this PR and the referenced issue as WONTDO

[Profpatsch]

I’d be okay with merging the change @JL0000 if you can clean up the history, squash everything into one commit and make it compatible with the current refactor branch.

[snaik20]

@JL0000 It seems like the PR contains a lot of unrelated commits, likely due to updating the base branch on GitHub. To resolve this, you can rebase your branch locally onto the latest refactor branch and then push the changes again.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud