Fix dynaconf's django integration

[pedro-psb]

Apparently it works if we follow the docs instructions to not set anything after the integration code. I'm probably the number one to blame on not having taken that seriously enough 🙈

Test PR: pulp/pulp_rpm#4521

📜 Checklist

• Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
• A changelog entry or entries has been added for any significant changes
• Follows the Pulp policy on AI Usage
• (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

[pedro-psb]

In general, if on setting depend on another setting, it should be inside a hook, and not after the dynaconf instantiation. For instance, FORBIDDEN_CHECKSUMS was not picking up the user provided ALLOWED_CONTENT_CHECKSUMS.

[ggainey]

Didn't realize this was a PR on 3.115 - we need this on main, please

[pedro-psb]

Yeah, I should have opened against main and then added the backport label.
Was caught in moment.

[pedro-psb]

#7893

[ggainey]

Great catch - and much cleaner than we were!

[patchback]

Backport to 3.115: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 3f395c1 on top of patchback/backports/3.115/3f395c1d25effcab0a5a69cc2d96b52cf559f42f/pr-7892

Backporting merged PR #7892 into 3.115

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulpcore.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.115/3f395c1d25effcab0a5a69cc2d96b52cf559f42f/pr-7892 upstream/3.115

4. Now, cherry-pick PR Fix dynaconf's django integration #7892 contents into that branch:

   $ git cherry-pick -x 3f395c1d25effcab0a5a69cc2d96b52cf559f42f

   If it'll yell at you with something like fatal: Commit 3f395c1d25effcab0a5a69cc2d96b52cf559f42f is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 3f395c1d25effcab0a5a69cc2d96b52cf559f42f

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix dynaconf's django integration #7892 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.115/3f395c1d25effcab0a5a69cc2d96b52cf559f42f/pr-7892

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[ggainey]

Backport to 3.115: 💔 cherry-picking failed — conflicts found

Can't backport to 3.115 when it's on 3.115 - who knew?!? :)