Work-around for Policy API Missing OrgUnit in Settings (0.4.1) release

[rlxdev]

🗣 Description

This contains the fix for the Policy API not including the orgunit with the policy setting in some rare cases. Google is looking into this issue, but this change will isolate us in the meantime. The basic rule for the policy settings is that the top-level orgunit has all the settings and any subunit or group will only have settings that deviate from the top-level orgunit's settings. It's appropriate to associate any setting without an orgunit with the top-level orgunit.

This also comes with the version update from 0.4.0 to 0.4.1.

Closes #599

🧪 Testing

Manual testing by faking out a setting without an orgunit. The setting gets the top-level orgunit.

The smoke test does not run successfully as of when this PR was created, because the meet 6.* baseline was added in a prior commit in the main branch and there's no corresponding Rego implementation.

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• If applicable, All future TODOs are captured in issues, which are referenced in the PR description.
• The relevant issues PR resolves are linked preferably via closing keywords.
• All relevant type-of-change labels have been added.
• I have read and agree to the CONTRIBUTING.md document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• Tests have been added and/or modified to cover the changes in this PR.
• All new and existing tests pass.

✅ Pre-merge Checklist

• This PR has been smoke tested to ensure main is in a functional state when this PR is merged.
• Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge Checklist

• Delete the branch to clean up.
• Close issues resolved by this PR if the closing keywords did not activate.

[adhilto]

@rlxdev Now that #607 is closed, is this ready for review?

[adhilto]

Tested after assigning a DLP policy to multiple OUs, which triggers the underlying bug this PR addresses. The issue was correctly handled and logged.

[mitchelbaker-cisa]

Generated report successfully.