Checks and fixes for pasting copied reference fields

[Logyrac]

Description

When copying and pasting values from a property's context menu, there were currently no checks in place to avoid certain issues:

• Attempting to paste to a property who's current value is null causes an error due to JsonUtility.FromJsonOverwrite
• Pasting a value from one type into a field of a different type, which may or may not have the appropriate fields

Added logic to check for potential conflicts and handle them.

Changes made

• Store the copied field type in SessionState for use in type safety comparisons
• Test for potential conflicts and return result as enum for handling
• Implement menu items for different results:
  • When no issues are detected or copied value is empty continue as before, with no change
  • When copied value is different type than current value, but still valid for the property, then pasting will create a new instance via Activator and then merge the JSON in. The Paste menu item shows a warning that the type will be overwritten.
  • When current value is null, create a new instance using Activator before using JSON overwrite to avoid error.
  • When copied value type is not valid for the field (uses TypeCandiateService [which is mis-spelled as a note, should be Candidate]) then disable the menu item with message explaining incompatible type.
  • When copied value refers to an invalid of non-existent type (type may be deleted between copy and paste) add disabled item with text stating invalid type
• Exposed function for evaluating qualification from TypeCandiateService, which evaluates the intrinsicTypePolicy and typeCompatibilityPolicy, for use in testing field combability in pasting, so that the TypeCandiateService is a single point of truth on this test.

[Logyrac]

Added support for pasting null values to the checks. When null is copied paste menu item will display warning that it will be set to null. If pasting null should be disallowed this is an easy change to revert.

On a separate note, it seems that most PRs recently are failing checks, the runner says the UNITY_LICENSE or UNITY_SERIAL secrets are unavailable. This is a safety restriction with GitHub and actions running on pull request, they can't access the secrets of either the source or target repository to prevent malicious PRs from potentially leaking that data (for example printing it to the test logs), but this does throw a wrench in game-ci's builder and test runner. PRs seemed to be working before so not sure what changed, as it stands right now the tests can't be ran reliably.

If I were to recommend an approach, instead of triggering the build and test checks on: pull_request to turn it into a command-executed action, so an approved moderator can issue a command in the comments like /run-tests to trigger. That would cause the checks to be ran in the context of the main repository, which means it would have access to secrets, and since it's manually ran by only trusted people the code can be reviewed first to make sure no malicious leaking code is present.

[Logyrac]

New pasting behaviour differed from previous logic and intent where users could paste values between types, so moved most paste options into submenus so both "Paste Type and Values" and "Paste Values Only" can be provided.

1. "Paste Type and Values" and equivalent are available when the copied and target type are compatible.
2. "Paste Values Only" and equivalent are available when the target is not null.
3. When copied type and target type are the same only the option for pasting values is provided as both would be functionally identical.
4. Those two options are renamed in the menu depending on context to more accurately represent what they do in that context.
   This allows the copy/pasting rules to still provide more type awareness while still allowing pasting values between different types.