Init django-flags

[jerabekjiri]

Issue: AAP-35418

Add django-flags dependancy to Hub component.

verifications:

1. add MY_FLAG to FLAGS in galaxy_ng/app/settings.py

FLAGS = {
    "MY_FLAG": []
}

2. enable, disable flag and verify state

> docker compose -f dev/compose/aap.yaml exec manager /bin/bash
bash-4.4# django-admin enable_flag MY_FLAG
Successfully enabled MY_FLAG

bash-4.4# pulpcore-manager shell
Python 3.11.10 (main, Sep 24 2024, 09:33:51) [GCC 8.5.0 20210514 (Red Hat 8.5.0-22)]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.29.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: from flags.state import flag_state, enable_flag, disable_flag

In [2]: flag_state('MY_FLAG')
Out[2]: True

In [3]: disable_flag('MY_FLAG')

In [4]: flag_state('MY_FLAG')
Out[4]: False

(django-flags in EDA: ansible/eda-server#1135)

[rochacbruno]

This is already by pulpcore, it we override we are going to break the browsable API I guess

https://github.com/pulp/pulpcore/blob/da11429a0ace2973beb3003d96a2a3071290ef52/pulpcore/app/settings.py#L131-L145

In the case we need to manipulate the setting coming from pulpcore we will need to do in the dynaconf_hooks.py which will run after data is loaded from pulpcore.

For now I think this can be removed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[patchback]

Backport to stable-4.10: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-4.10/f4faf422a54cba2e26415997637e8cb6e008fd3f/pr-2374

Backported as #2383

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