Add unit test for createModeledMethodKey

[shati-patel]

Follow up to #3518 to add some tests! 🧪

I'm not really sure what else to test 🤔 Suggestions welcome ❤️

Checklist

N/A, no user impact

• CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
• Issues have been created for any UI or other user-facing changes made by this pull request.
• [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

[koesie10]

Thanks!

For additional tests, I think you might be able to get some inspiration from the validation.test.ts unit tests:

• A test that checks that the provenance field is always set to manual, regardless of the actual provenance
• A test that checks that "unused" fields (e.g. an input field on a source model) are ignored. It might be useful to repeat this for source, sink, summary and neutral, like in validation.test.ts.

[koesie10]

This should result in better error messages:

Suggested change

	expect(modeledMethod === modeledMethod2).toBe(false);
	expect(key === key2).toBe(true);
	expect(modeledMethod).not.toBe(modeledMethod2);
	expect(key).toEqual(key2);

[shati-patel]

Thank you for the pointers, @koesie10! I've added some more tests 🧪

[koesie10]

Thanks!