Avoid treating modules as changed, when only their tests have been updated

[JamesDawson]

If a modules tests include references to other modules that have been changed, then the JSON files associated with those tests get updated.

The publishing logic sees those updates files and considers it as an update to the module, however, the NerdBank versioning does not and won't increment the version number which results in an error when the build tries to publish a version that already exists.

Ref: https://github.com/endjin/Endjin.RecommendedPractices.Bicep/actions/runs/10042611254/job/27753446515

Changed modules:
general/app-configuration
general/key-vault-with-secrets-access-via-groups
general/key-vault
general/storage-account
general/synapse-workspace
Processing module: general/app-configuration
  Published - OK
fatal: tag 'general/app-configuration/1.0.3' already exists
WARNING: Error tagging module 'general/app-configuration' with 'general/app-configuration/1.0.3'