Introduction of devcontainer and GitHub Codespaces for easier execution of btpsa

[lechnerc77]

Purpose

• Introduce Codespaces for an easier setup of the btpsa

Does the PR solve an issue

[ ] Yes - Please add issue number
[X] No

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Option 1: devcontainer

• Clone the repo

• Start a dev container

• Open a Codespace based on one of the given dev containers

What to Check

Verify that the following are valid

You can access the btpsa in the devcontainer /Codespace

Other Information

• The Badges for "Open in Codespace" can be updated only after the branch is merged into dev and main (see https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/adding-a-codespaces-badge)
• Be aware of billing when using Codespaces: https://docs.github.com/en/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces

[cla-assistant]

All committers have signed the CLA.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ lechnerc77
❌ [btpsa bot] docu generation

---

[btpsa bot] docu generation seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}