New APV workflow backend to remove need for ProbeReferenceVolume component from user side

[FrancescoC-unity]

This PR is a refactor of how the workflow for APV works so that we can move away from the ProbeReferenceVolume component workflow.

Starting with the TL;DR: Essentially now the ProbeReferenceVolume component is purely a UX to input values, but they are now sent immediately to a centralized system that handles all the data. Meaning that if we have a UX somewhere else to input data (@alelievr is on the frontend now) we don't need the probe reference volume component.

A bit of a longer:

• Now every scene with a probe volume in it will have a completely hidden component created. This will own a bunch of assets, one per state (concept of state not here yet).
• This component is going to queue and unqueue assets to be loaded, somewhat similarly to what the authoring component was doing before.
• The profile is now a completely editor only concept, it doesn't need to be loaded at runtime and everything that is needed at runtime is stored on the asset itself.
• The baking settings and profile are serialized for editor usage in a centralized asset indexed with Scene GUID.
• Everything that was using the authoring (ProbeReferenceVolume) component is now not using it at all, so as soon as we have UX for user to input data, the backend is ready.

[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)

HDRP
/.yamato%252Fall-hdrp.yml%2523PR_HDRP_trunk

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_trunk
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.