Change import path to `django_csp` - breaking change

[robhudson]

In pull request #219, I’ve refactored the settings configuration to support both the enforced CSP header and the report-only CSP header. Please note, this is a backwards incompatible change.

To minimize disruptions over multiple releases, I propose making multiple backwards incompatible changes at once. Specifically, I suggest changing the import path from csp to django_csp, aligning with common practices for Django apps.

I’m opening this issue for discussion. Please share any feedback, whether in favor or against.

Thank you!

[robhudson]

I looked more closely at popular Django apps and it isn't actually as common as I thought to include the django_ prefix in the module name for import. I think it's just that csp has such few words that it makes it feel like more of a scarce space.

Anyway, I'll close this. If there's ever any import path conflicts in the future we can reconsider.