list/MMv1: unionize allProps within listScope to include url_param_only values

[BBBmau]

We run into a case found in

• kms: add list resource for crypto_key_version #17984
  where extracting from just import_format was not enough due to the resulting list_resource_generation being empty in it's CryptoKeyVersionTypeModel.

List scope detection previously only used identity/import fields, so required URL-only scope values (like crypto_key) were missed.

This change includes all relevant properties when deriving list scope, deduplicates matches, and adds a regression test for the CryptoKeyVersion pattern.

Needed to merge #17984 as it becomes passing afterwards

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes for commit dc0c682:

Diff report

Your PR hasn't generated any diffs, but I'll let you know if a future commit does.

[melinath]

Just to make sure I understand this correctly - what exactly is a ListScope? It looks like IdentityProperties is specifically related to Resource Identity, which is also a core part of list resources, but is different from list scope?

To put this another way: is this a problem with ListScopeProperties or a problem with IdentityProperties? If a particular field is in base_url but not in import_format, wouldn't that need to still be part of the resource identity?