[ShaderGraph] [2022.1] Making noise nodes platform deterministic

[cdxntchou]

Original PR here: #5452
Switched branches so I could rebase off of a passing master build.

Purpose of this PR

Fix for bug: https://fogbugz.unity3d.com/f/cases/1156544/

Console PR: https://github.cds.internal.unity3d.com/unity/ScriptableRenderPipelinePrivate/pull/234

Introduces a set of deterministic integer hashes, with varying input and output dimensions.
These hashes are integer based, so they produce the same result on ALL platforms.

Converted noise nodes to have enum switches to choose between legacy hash behavior, and the new deterministic hashes.
Existing noise nodes will use legacy behavior for backwards compatibility, newly created nodes choose deterministic by default.

New deterministic hashes also have a more random appearance: (legacy hash looks bad on nvidia cards)

Doc ticket added here: https://jira.unity3d.com/browse/GSG-548

---

Testing status

Added new test cases to the Procedural test scene, to test both legacy and deterministic versions of the noise nodes.
(noise node tests were previously disabled... enabled them)

Validated existing noise nodes upgrade with identical results, using the legacy hashes.

Tested newly created noise nodes, default to deterministic hashes:

Yamato:

ShaderGraph: 🟢
https://yamato.cds.internal.unity3d.com/jobs/902-Graphics/tree/sg%252Ffix%252Fnoise2/.yamato%252Fall-shadergraph.yml%2523Nightly_ShaderGraph_2021.2/8494066/job/pipeline
Master: 35e38b1
https://yamato.cds.internal.unity3d.com/jobs/902-Graphics/tree/master/.yamato%252Fall-shadergraph.yml%2523Nightly_ShaderGraph_2021.2/8364525/job/pipeline

ShaderGraph Trunk: 🟢
https://yamato.cds.internal.unity3d.com/jobs/902-Graphics/tree/sg%252Ffix%252Fnoise2/.yamato%252Fall-shadergraph.yml%2523PR_ShaderGraph_trunk/8664161/job/pipeline
Master: 9f86ed3
https://yamato.cds.internal.unity3d.com/jobs/902-Graphics/tree/master/.yamato%252Fall-shadergraph.yml%2523PR_ShaderGraph_trunk/8643605/job/pipeline

Console Tests: 🟡 - same failures as master
https://github.cds.internal.unity3d.com/unity/ScriptableRenderPipelinePrivate/pull/234

---

Comments to reviewers

Notes for the reviewers you have assigned.

[github-actions]

Hi! This comment will help you figure out which jobs to run before merging your PR. The suggestions are dynamic based on what files you have changed.
Link to Yamato: https://yamato.cds.internal.unity3d.com/jobs/902-Graphics
Search for your PR branch using the sidebar on the left, then add the following segment(s) to the end of the URL (you may need multiple tabs depending on how many packages you change)

Shader Graph
/.yamato%252Fall-shadergraph.yml%2523PR_ShaderGraph_2021.2
Depending on your PR, you may also want
/.yamato%252Fall-shadergraph_builtin_foundation.yml%2523PR_ShaderGraph_BuiltIn_Foundation_2021.2
/.yamato%252Fall-shadergraph_builtin_lighting.yml%2523PR_ShaderGraph_BuiltIn_Lighting_2021.2

SRP Core
You could run ABV on your branch before merging your PR, but it will start A LOT of jobs. Please be responsible about it and run it only when you feel the PR is ready:
/.yamato%252F_abv.yml%2523all_project_ci_2021.2
Be aware that any modifications to the Core package impacts everyone in the Graphics repo so please discuss the PR with your lead.

Depending on the scope of your PR, you may need to run more jobs than what has been suggested. Please speak to your lead or a Graphics SDET (#devs-graphics-automation) if you are unsure.

[bencloward]

This is going to improve out noise a lot. Thanks, Chris!

[sarah-welton]

Docs changes are in as requested. Seems like a great change, and happy to see it!

[jessebarker]

LGTM

[sarah-welton]

Forgot I already reviewed because I still had this open. Ignore me