Add allowed_ prefix to some model and form field arguments

[blag]

As discussed in PR #54, make model and form field arguments slightly more explicit with what they are: allowlists or denylists.

I'll rebase this once #54 is merged.

[Copilot]

Pull Request Overview

This PR adds clarity to model and form field arguments by prefixing certain parameters with "allowed_" to explicitly indicate they are allowlists rather than denylists.

• Renames ambiguous parameters to be more explicit about their allowlist nature
• Updates template tag parameter for consistency
• Maintains backward compatibility while improving API clarity

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/django_nh3/templatetags/nh3_tags.py	Renames tags parameter to allowed_tags in template filter
src/django_nh3/models.py	Updates model field parameters with allowed_ prefix and reorganizes initialization
src/django_nh3/forms.py	Updates form field parameters with allowed_ prefix and reorganizes initialization
src/django_nh3/utils.py	Adds utility functions and normalizes options handling
tests/test_settings.py	Adds comprehensive tests for the new option normalization functionality

Comments suppressed due to low confidence (1)

tests/test_settings.py:90

• This test duplicates the logic from lines 79-80. The second test should use the string import path as intended in the test setup, not the function reference again.

        result = normalize_nh3_options({"attribute_filter": set_test_flag_true})

[Copilot]

The function has disabled complexity warnings (C901, PLR0912) indicating it may be too complex. Consider breaking this function into smaller, more focused functions to improve maintainability.