Avoid AllowAny on unsafe DRF methods
DRF views that accept POST, PUT, PATCH, or DELETE should not declare `AllowAny` unless the endpoint is intentionally public.
#Metadata
#Why it matters
Open unsafe methods allow unauthenticated clients to mutate data and violate least-privilege API access.
#Remediation
Require authentication or scoped permissions for unsafe verbs unless the handler is explicitly public and documented.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/python/py.security.drf-allow-any-unsafe-method.rule.yaml.