Add Bazel CI workflow and buildifier formatting

[DominikAFischer]

ℹ️ NOTE: The bulk of the changes made by this PR is the automatically generated Bazel lockfile: +2615 / -1

Add Bazel CI workflow and buildifier formatting:

• Add bazel github action workflow, which currently contains these checks:
  • Smoke test: bazel version
  • Stale lockfile check: bazel mod deps --lockfile_mode=error
  • Bazel format check: bazel run //:format_check
  • Query all bazel targets: bazel query //...
  • Build all targets for host platform: bazel build //...
  • Build all targets for example embedded platform: bazel build --config=s32k148 //...
  • Run all bazel tests: bazel test //...
• Refactored all workflows to use a shared setup-docker-env composite action for Docker image build and Bazel cache directory setup.
• Add buildifier_prebuilt 8.5.1.1 dev dependency to MODULE.bazel
• Add //:format_check and //:format_fix targets via buildifier_prebuilt
• Add buildifier to Docker image and add it as a formatter to treefmt.
• Apply Bazel file formatting fixes

---

NOTE: Docker bind mount permission issues:
Bazelisk/Bazel cache directories created by Docker bind mounts via create_host_path: true are owned by root, causing permission errors for the unprivileged container user. It seems this is a fundamental, unresolved Docker Engine limitation (moby/moby#2259 has been open since 2013).
Instead create_host_path: false is used and it's the users responsibility to set up the cache dirs locally. This will be added to the README and Bazel quick start guide once the Bazel related sections are added.

---

NOTE: We have decided to keep two instances of buildifier for now:

• Docker instance for treefmt support
• Bazel module instance for native Bazel formatting/linting

[DominikAFischer]

False positive / flaky test uds/test_udsToolRDBI.py::test_rdbi[posix] in workflow Run pytest for posix platform / run-pytest-on-posix identified.
Increasing this timeout fixes the issue and confirms the root cause. For a proper fix this timeout should be replaced by properly handling it using either polling or something like pexpect.
EDIT: The issue has been raised to the maintainer and a proper fix is underway.

[christophruethingbmw]

Looks good to me, just wait for the fix of the flaky test, PR for that should come soon.