fix: [Graphics] Fix light component API

[Eideren]

PR Details

LightComponent.Light.Shadow is an abstract LightShadowMap shared across all light types, the light rendering logic expects specific combination of shadow types per light types. So, users could set LightPointShadowMapRendererCubeMap on a Directional Light for example, leading to unexpected rendering issue or exceptions.
This change ensures that each light's shadow can only be set to a supported shadow map type.

Motivation and Context

Fixes poor usage of inheritance and composition principles. There's more work on the XShadowMapRenderer side, but while that logic isn't that well written, it won't crash on us.

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix
• New feature
• Breaking change - users will no longer be able to set unexpected shadowmap types. Or reference DirectLightBase as that type has been removed, I could resurrect it as long as it doesn't implement IDirectLight, but it wouldn't be very useful then.

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[Doprez]

I did a quick test to see if I could recreate the issue and it seems better right now.
Directional light has the proper Shadow map assigned

And spotlight also seems correct

Only thing I didnt test was if I were to add a new shadowmap if the dropdown would appear again. But I dont have a secondary I could test with, I guess I could just make a duplicated shadow map of one of these and see.

Edit: I didnt realise the change would assign the ShadowMap directly. So you would have to create a new Light by inheriting ColorLightBase and IDirectLight. This makes sense to me but maybe @tebjan should speak on this for the rendering side?

[Eideren]

Thanks a bunch for reviewing @Kryptos-FR :)