Fix Style color object for IconStyleOptions.

[Horndev]

• OL js represents RGBA as int array and setting Color breaks JSInterop when string. This is due to an object seriallizatoin error if color is not null for methods such as new feature added, or feature clicked.
• Future extensions could include allowing Color application along with other style options in the SetCustomImageStyle method.
• Setting the style color allows image markers to be tinted.

Without public access to Color, the style can now be set for image markers:

newMarker.Styles[0].Icon.Color = new int[] { 125, 0, 0, 255 }; // For example

The effect is that the same image (icon) can be used to represent different things but styled with different color tints.

Possible alternative could be to create a custom Json Serializer that maps string RGB / Hex values in C# with int[] arrays being serialized on js side. Passing a string to color does almost work, but any JSInterop calls break as OL converts the strings to int arrays in the js object (causing serialization back to C# object to fail).

[lolochristen]

Thanks for your PR and input. The Color object is indeed an array of int. At other places it supports the object ColorLike which is a string, but not here. To make this all proper, I suggest having a Color struct on the Blazor side, which is internally an array but supports assigning strings to keep compatibility. However, I'll approve your PR because for IconStyle.Color only colors as arrays are accepted by API. thx

[Horndev]

Thanks for your PR and input. The Color object is indeed an array of int. At other places it supports the object ColorLike which is a string, but not here. To make this all proper, I suggest having a Color struct on the Blazor side, which is internally an array but supports assigning strings to keep compatibility. However, I'll approve your PR because for IconStyle.Color only colors as arrays are accepted by API. thx

I agree! This is more of a quick fix that "makes thing work" for now without breaking anything else. A full solution should be implemented, like you point out. Thanks :)