package_registry_access_level is ignored during project creation
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=572010)
</details>
<!--IssueSummary end-->
<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "type::bug" label:
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Despite a project is created via the GitLab API with
```
"package_registry_access_level": "disabled",
```
the package registry is still available.
### Steps to reproduce
Post the following to create a project with only repository features enabled:
```bash
curl -X POST --location "https://gitlab.com/api/v4/projects"
-H "Content-Type: application/json"
-H "Private-Token: ..."
-d '{
"name": "My New Project",
"path": "my-new-project",
"description": "A sample project created via GitLab API",
"visibility": "private",
"initialize_with_readme": false,
"analytics_access_level": "disabled",
"builds_access_level": "disabled",
"container_registry_access_level": "disabled",
"environments_access_level": "disabled",
"feature_flags_access_level": "disabled",
"infrastructure_access_level": "disabled",
"issues_access_level": "disabled",
"model_experiments_access_level": "disabled",
"model_registry_access_level": "disabled",
"monitor_access_level": "disabled",
"package_registry_access_level": "disabled",
"pages_access_level": "disabled",
"releases_access_level": "disabled",
"requirements_access_level": "disabled",
"security_and_compliance_access_level": "disabled",
"snippets_access_level": "disabled",
"wiki_access_level": "disabled",
"repository_access_level": "enabled",
"forking_access_level": "enabled",
"merge_requests_access_level": "enabled",
"lfs_enabled": false
}'
```
The answer includes
```
"packages_enabled": true,
...
"package_registry_access_level": "private",
```
### Example Project
<!-- If possible, please create an example project here on GitLab.com that exhibits the problematic
behavior, and link to it here in the bug report. If you are using an older version of GitLab, this
will also determine whether the bug is fixed in a more recent version. -->
### What is the current *bug* behavior?
The package registry isn't disabled as requested.
### What is the expected *correct* behavior?
The package registry should be disabled.
### Relevant logs and/or screenshots
<!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
as it's tough to read otherwise. -->
### Output of checks
<!-- If you are reporting a bug on GitLab.com, uncomment below -->
This bug happens on GitLab.com
<!-- and uncomment below if you have /label privileges -->
<!-- /label ~"reproduced on GitLab.com" -➔
<!-- or follow up with an issue comment of `@gitlab-bot label ~"reproduced on GitLab.com"` if you do not -->
#### Results of GitLab environment info
Reproduced on a GitLab 18.2 CE as well.
#### Results of GitLab application Check
<!-- Input any relevant GitLab application check information if needed. -->
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
(we will only investigate if the tests are passing)
</pre>
</details>
### Possible fixes
<!-- If you can, link to the line of code that might be responsible for the problem. -->
### Patch release information for backports
If the bug fix needs to be backported in a [patch release](https://handbook.gitlab.com/handbook/engineering/releases/patch-releases) to a version
under [the maintenance policy](https://docs.gitlab.com/policy/maintenance/), please follow the steps on the
[patch release runbook for GitLab engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md).
Refer to the [internal "Release Information" dashboard](https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1)
for information about the next patch release, including the targeted versions, expected release date, and current status.
#### High-severity bug remediation
To remediate high-severity issues requiring an [internal release](https://handbook.gitlab.com/handbook/engineering/releases/internal-releases/) for single-tenant SaaS instances,
refer to the [internal release process for engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/internal-releases/engineers.md?ref_type=heads).
<!-- If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"` -->
issue