Backport of 'New projects inherit parent value for duo_features_enabled'

What does this MR do and why?

• Backport for MR merged to master here: New projects inherit parent value for duo_featu... (!199042 - merged)
• This fixes the following situation: an instance or group on an instance has Duo Features set to "default off". A new project is created in the instance or group. Before this MR, that project would default to having Duo Features turned on. Now, they will be correctly turned off.
• More information on Duo Features setting: https://docs.gitlab.com/user/gitlab_duo/turn_on_off/
• This same setting also apples to Amazon Q for GitLab instances using Amazon Q instead of GitLab Duo.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
• [c] The MR title is descriptive (e.g. "Backport of 'title of default branch MR'"). This is important, since the title will be copied to the patch blog post.
• Required labels have been applied to this merge request
  • severity label and bug subtype labels (if applicable)
  • If this MR fixes a bug that affects customers, the customer label has been applied.
• Set the milestone of the merge request to match the target backport branch version.
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the e2e:test-on-omnibus-ee job has either succeeded or been approved by a Software Engineer in Test.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).