Add support for profiles to Solvers

[gejohnst]

Configuring a solver currently requires a lot of tweaking to ensure the behavior feels right, and copying settings between solvers is an involved process. By adding profiles to solvers, the configuration data becomes separated from the functionality and can easily be shared within and between projects. This allows for faster development and more consistency for consumers of the MRTK. This also allows for default configurations to be packaged with the MRTK alongside common use cases.

To support backwards compatibility, these profiles will act as override values for the existing settings when both are present. There will also exist an easy means to store preexisting settings as a profile for older projects to facilitate upgrading to this system.

[keveleigh]

Related to #2798

[Troy-Ferrell]

Why does copy component not work for this scenario? The serialized object is effectively a profile.

[Zee2]

Closing as not planned; we won't be using profiles for solvers, but we may end up offering ScriptableObject support.