feat: Add PUT endpoint for products and related tests

[mtruj013]

Done

• Added PUT endpoint for products and related tests
• Drive-by's:
  • Fixed redundant error on create_product_deployment
  • Refactored name normalisation logic into a shared NormalizeNameMixin

QA

• See that tests pass
• For a more thorough QA:
  • Run the site using the command dotrun
  • Add a couple deployments and see that everything passes as intended, sample curls here

Issue / Card

https://warthogs.atlassian.net/browse/WD-33171

[muhammad-ali-pk]

Nit: Probably better to print a specific error (which in this could be along the lines of "failed to update/save product", considering the single operation in the try block). Helps quick debugging and pinpointing the concerned block.

[mtruj013]

Not sure I agree, 500s are by nature catch-alls for unexpected failures, so keeping the message generic is intentional. The specific error would be visible in server logs, which is the right place for debugging internals rather than exposing them in API responses (which could also turn into a security concern for server level issues)

[muhammad-ali-pk]

As slug will always remain the same despite the name, why is that desirable?

[mtruj013]

Good question, it's an intentional decision for a couple reasons. Product name changes are extremely rare so any name/slug drift is equally rare and manageable, and slugs are used as path parameters across most endpoints, so regenerating them on name change would break any existing URLs, scripts, or integrations pointing at the old slug without giving the user any warning