fix: correctly parse multi-value list flags in setup_config

[nishantxscooby]

Fixes #499

Fix multi-value flag parsing in setup_config

Problem
List values passed via --append, --override, and --remove were parsed using naive comma splitting, which breaks quoted values with spaces and ISO2 country codes.

Solution
Use ast.literal_eval to safely parse list literals, with a fallback to the previous comma-based logic for backward compatibility.

Scope

• Single-file change
• No validator changes
• No migrations
• No formatting-only changes

Testing
Parsing logic was validated directly for:

• multi-value lists with spaces
• ISO2 country codes
• booleans, numbers, and fallback behavior

[nishantxscooby]

Hi @Lorygold 👋

This PR is a clean restart for issue #499 with a very narrow scope.
I’ve limited the change to a single file and avoided any formatter or unrelated changes.

The fix replaces naive comma-splitting with ast.literal_eval (with a backward-compatible fallback) to correctly handle multi-value flags, quoted strings, and ISO2 country codes.

Thanks for reviewing :)

[Lorygold]

Are you sure that it works? I get:

$ ./manage.py setup_config -a filtered_alerts_types=['New Device', 'User Risk Threshold', 'Anonymous IP Login']
usage: manage.py setup_config [-h] [--version] [-v {0,1,2,3}] [--settings SETTINGS] [--pythonpath PYTHONPATH] [--traceback] [--no-color] [--force-color] [--skip-checks]
                              [--execution_mode {manual,automatic}] [-o FIELD=[VALUES]] [-r FIELD=[VALUES]] [-a FIELD=[VALUES]] [--set-default-values] [--force]
manage.py setup_config: error: unrecognized arguments: User Risk Threshold, Anonymous IP Login]

Test it locally and add a test in the test_management_commands.py with that command-line to check the correct behavior

[nishantxscooby]

Hello, I think you're right, and I've been trying to fix this up lately but seems like am again stuck in the CI checks loop, can you please help me get out of this loop?

thankyou :)

[Lorygold]

You can follow the CONTRIBUTING.md file for linters troubleshooting. Did you run them locally? Which are the results and the linters versions?

[nishantxscooby]

Hello, okay - thanks for the guidance. I'll look into it as soon as possible, am out for next 3-4 days. Sorry for the inconvenience.

[Lorygold]

@nishantxscooby please close this PR, since you opened another one.

for next times, work on the same PR, it's not necessary to open a new one, changes can be done in the original one

[nishantxscooby]

Hey! @Lorygold

Sure, I'll keep that in mind, sorry for the chaos.

Also please assign with some issue which are available at moment.

Thankyou :)