.NET errors appear after upgrading to 2024.12.1 and can no longer access web vault

### Steps To Reproduce

1. Go to bitwarden self-hosted URL
2. Browser returns "502 Bad Gateway" nginx/1.27.3

### Expected Result

Should be able to access the latest unified self-hosted beta web vault.

### Actual Result

Browser returns "502 Bad Gateway" nginx/1.27.3

Looking at the logs for the Bitwarden container shows the following;

```handlebars
Adding group `bitwarden' (GID 20166) ...
Done.
Adding user `bitwarden' ...
Adding new user `bitwarden' (20162) with group `bitwarden (20166)' ...
Not creating home directory `/home/bitwarden'.
Adding new user `bitwarden' to supplemental / extra groups `users' ...
Adding user `bitwarden' to group `users' ...
You must install or update .NET to run this application.

App: /usr/local/bin/hbs
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64)
.NET location: /usr/share/dotnet

The following frameworks were found:
8.0.1 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Learn more:
https://aka.ms/dotnet/app-launch-failed

To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=linux-x64&os=debian.12
```

This problem was not present in the 2024.12.0 beta release.
I would appreciate assistance with this as I'm not sure how to proceed. (For now I have reverted to 2024.12.0 and everything is fine again)

### Screenshots or Videos

_No response_

### Additional Context

_No response_

### Githash Version

https://{your-bitwarden-domain}/api/config and copy the gitHash version

### Environment Details

Container-Optimized OS from Google version 101
Docker 20.10.27

### Database Image

MariaDB version 11.6.2

### Issue-Link

https://github.com/bitwarden/server/issues/2480

### Issue Tracking Info

- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Start by comparing the 2024.12.0 and 2024.12.1 self-hosted container configuration and reviewing the Bitwarden container startup logs around `/usr/local/bin/hbs`. Confirm the .NET runtime expected by the application is available, then verify that the web vault loads without the 502 error on the reported environment.

Written by the indexing model from the issue text.