chore: fix #412 #622 iOS resolver reference when iOS module not installed

[StephenHodgson]

• fixes [BUG] Unable to resolve reference 'UnityEditor.iOS.Extensions.Xcode' on Windows #412
• fixes [Bug] IOSResolver.dll tries to load on Windows/Linux - causes error #622
• updated export_unity_package_config.json and separated Google.IOSResolver.* into its own PluginImporter section, adding defineConstraints key with UNITY_EDITOR and UNITY_IOS elements.
• lint export_unity_package_config.json with standard json lint, 2 spaces
• added defineConstraints to AssetConfiguration in export_unity_package.py
• added unit tests for defineConstraints in export_unity_package_test.py
• updated workflows to use latest version of checkout/setup actions

Fixes

Assembly 'Packages/com.google.external-dependency-manager/ExternalDependencyManager/Editor/1.2.183/Google.IOSResolver.dll' will not be loaded due to errors:
Unable to resolve reference 'UnityEditor.iOS.Extensions.Xcode'. Is the assembly missing or incompatible with the current platform?
Reference validation can be disabled in the Plugin Inspector.

Invalid when platform is not set to IOS or module not installed

Valid when platform is set to IOS

CC @a-maurice, @chkuang-g

[Grimeh]

Unless I'm misunderstanding how the package config works, shouldn't be in the new section below? This currently looks like it affects:

• Google.JarResolver.*
• Google.VersionHandlerImpl.*
• Google.PackageManagerResolver.*

And not:

• Google.IOSResolver.*

[Grimeh]

(also thanks for taking the time to fix this issue properly, it's annoying to manually fix this for each project I work on that uses EDM4U)

[StephenHodgson]

Unless I'm misunderstanding how the package config works, shouldn't be in the new section below?

Yes it is now split out into its own section. It is just how GitHub is displaying it. If you look at it side by side you'll see the difference.