X pipeline - When editing a light preset, the light type was disabled

[alex-vazquez]

Purpose of this PR

• Fix 1358733

The scope was handling a property from the additional camera data

---

Testing status

Check light presets save, apply and edit. Also check normal light inspector.

---

Comments to reviewers

@Unity-Technologies/gfx-qa-hdrp Test the preset edition of the lights, and the light inspector

[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_2021.2

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.

[jenniferd-unity]

This PR integrates the flow of Presets as something permanent. I am worried about the impact of integrating a workaround as something not temporary (even if we aim to remove it and never know when it will land).
Any fields for Preset are supposed to be supported. The previous PR aims to rectify our UI to show that some fields are not properly supported without having to check the doc or file a bug because of a preset not being fully applied/working.

[remi-chapelain]

Only unexpcted thing I noticed while testing this, is when you select area light in the light preset, it's not saved and it will default to point when de-selecting the preset.

71500713312d381723acba8d812cc148.mp4

[remi-chapelain]

Issue fixed ! All good ✔️

[alex-vazquez]

Yamato is green despite the fact that the CI is not being updated on the PR.