bugfix: ContentIndicator validation should be on "name", not on "type".

[decarteret]

Prior implementation was ensuring only one indicator "type" per collection which is not correct.

The goal is to have:

• all the items from contentIndicators
• all the items from defaultContentIndicators that aren't in contentIndicators
• the defaultContentIndicators should be first

This PR produces the correct calculation.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to
know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI

You can read more details in our
Responsible AI Policy

Review Checklist

Before merging, the reviewer should check the following items:

• Does the PR do what it claims to do?
• If this is a new adaptor, added the adaptor on marketing website ?
• If this PR includes breaking changes, do we need to update any jobs in
  production? Is it safe to release?
• Are there any unit tests?
• Is there a changeset associated with this PR? Should there be? Note that
  dev only changes don't need a changeset.
• Have you ticked a box under AI Usage?

[josephjclark]

@decarteret I've pushed some commits to fix some test failures in CI.

Could you please run pnpm changeset from root and follow the prompt to generate a public release note for the change? This looks like a patch version to me.