resourceIdentity/MMv1: skip id values that aren't present in resource schema

[BBBmau]

When looking into list mmv1 i noticed a bug where an import_format can be used despite the values not being present in the resource's schema.

This adds a check to prevent schema field from being included in identity schema. An example of this is alloydb_user not including project in the resource schema:

magic-modules/mmv1/products/alloydb/User.yaml

Lines 22 to 28 in 59d0a15

	base_url: '{{cluster}}/users'
	self_link: '{{cluster}}/users/{{user_id}}'
	create_url: '{{cluster}}/users?userId={{user_id}}'
	update_verb: 'PATCH'
	update_mask: true
	import_format:
	- 'projects/{{project}}/locations/{{location}}/clusters/{{cluster}}/users/{{user_id}}'

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 9098981:

Diff report

Your PR generated the following diffs in downstream repositories:

Repository	Diff Link	Changes
google provider	View Diff	8 files changed, 8 deletions(-)
google-beta provider	View Diff	8 files changed, 8 deletions(-)