new feature: set arbitrary layer properties

[m0nac0]

This introduces a new method: MaplibreMapController#setLayerProperties to change any properties of any given layer at runtime.

I had to fix LayerPropertyConverter for android and iOS because there was a problem with the visibility property (which gets somewhat special treatment, and did not work because it received a string like ""visible"" instead of "visible" (notice the unnecessary quotes)). In the process I also fixed the script to generate these files.

TODO:

• update example app to test other properties and layer types

[m0nac0]

Note for review: this file was automatically generated by the script.
Apparently it was manually formatted in the past, but I did not do this again.
It is much easier to review when enabling "hide whitespace changes"

[m0nac0]

also automatically generated

[m0nac0]

Closes #250

[JulianBissekkou]

@stefanschaller can you take a look?

[stefanschaller]

Suggested change

	try {
	_map.setLayoutProperty(layerId, entry.key, entry.value);
	} catch (e) {
	print('Caught exception (usually safe to ignore): $e');
	}
	try {
	_map.setPaintProperty(layerId, entry.key, entry.value);
	} catch (e) {
	print('Caught exception (usually safe to ignore): $e');
	}
	try {
	_map.setLayoutProperty(layerId, entry.key, entry.value);
	_map.setPaintProperty(layerId, entry.key, entry.value);
	} catch (e) {
	print('Caught exception (usually safe to ignore): $e');
	}

[m0nac0]

I think with your suggestion, if it is a paint property, the setLayoutProperty method would (usually?) throw an error and the setPaintProperty method would not be called.

[m0nac0]

@stefanschaller What do you think, is it fine to keep the code as is with that explanation?

[stefanschaller]

Looks good to me. I didn't have any issues with the layer api @JulianBissekkou

[m0nac0]

@stefanschaller @JulianBissekkou Can we merge this?