Color Palette Names are unique across the application

[sosiology]

Description

If a color palette name already exists (even if it's from another user), the palette doesn't get saved (e.g., "BAKOM 1234").

Reported by Nick in Gitlab here: https://gitlab.ldbar.ch/bafu/visualize/-/issues/377#note_18850

To Reproduce Steps to reproduce the behavior:

1. Go to test.visualize.admin.ch
2. Login
3. Go to Color Palette
4. Create a color palette with the name Emma's Color Palette
5. See that color palette cannot be saved as the name is already used by another user (me)

Expected behavior
Color palette names should be unique to a user not across the application (unless of course in future this could allow color palettes to be be shared across applications).

Environment (please complete the following information):

• Visualize environment and version: v5.8.1 (01495c7)
• Browser and version [e.g. Chrome 132]

[bprusinowski]

Moving to Blocked, as the change to database schema could potentially result in a loss of data, which means we need to handle it in a bit more careful way – we'll discuss this with @adintegra next week.

[bprusinowski]

Related issue: #2360

[adintegra]

Re-discussed this issue in the weekly and all parties agreed to leave the current functionality in place – i.e. continue to enforce unique palette names. Also, considering the potential future expansion of this feature to enable shared palettes across user groups or organisational units, stakeholders believe unique palette names make sense for the foreseeable future.

However, the linked enhancement request should be kept open as it would still be beneficial to align database patterns and streamline the current design regardless.