Feature: Setup "Default Palette Modules" in a template

[Steve-Mcl]

Description

Permit platform admin to setup templates with Default Palette Modules ready for new instance creation.

• Some refactoring to reduce code duplication
  • Re-use the PaletteModules.vue section in a new page packages/flowforge/frontend/src/pages/admin/Template/Palette.vue
  • Move the logic for comparing editable vs original palette modules to packages/flowforge/frontend/src/pages/admin/Template/utils.js and export it as comparePaletteModules
• Update server side logic in forge/db/controllers/ProjectTemplate.js validateSettings to also check palette.modules for duplicate names, invalid names, invalid versions (using same regex as frontend checks)
• Add tests for all of the above

Project controller
    getRuntimeSettings
      ✔ does not merge template palette modules into runtime settings

  Project Template controller
    Validate Settings
      palette.modules
        ✔ accepts valid values
        ✔ rejects invalid name
        ✔ rejects invalid version
        ✔ rejects duplicate name

  Project API
    Create project
      ✔ Create a project // (modified to check palette modules are duplicated from template)
      ✔ Should not merge template modules into existing instance runtime settings

As far as I can see, adding modules are already mentioned in the docs

• here: https://flowforge.com/docs/admin/#managing-templates
• and here: https://flowforge.com/docs/user/concepts/#template
  Not sure if this should be expanded on - considering docs "done" unless told otherwise.

Related Issue(s)

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated NO see above
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on flowforge/helm to update ConfigMap Template
  • Issue/PR raised on flowforge/CloudProject to update values for Staging/Production

Labels

• Backport needed? -> add the backport label
• Includes a DB migration? -> add the area:migration label

[knolleary]

Looks good except for all the linting warnings to tidy up.

[Steve-Mcl]

Looks good except for all the linting warnings to tidy up.

Urggg - Didn't even spot them 😄

Done now.

[Steve-Mcl]

@knolleary all linting issues resolved and all tests passing now.

Re-review requested. Ta.