Components and actions in the config should also be case-insensitive

[Tiagoperes]

The name of the components or actions that come from the backend are case-insensitive, but the internal Beagle configuration is not. This can be very confusing for developers, because, when they are in the backend, the case doesn't matter, but when they're making their beagle config in the front-end, the name does matter.

For instance, if the dev wants to use the component screen, in the backend he/she can write beagle:SCreeNcomponent, it will work. In the front-end config, if the dev wants to replace the default behavior of the screen, he/she MUST write beagle:screencomponent. If any case is wrong, the component won't be replaced and the dev will have no idea why, because he/she doesn't even know what the "correct" case is.

[hectorcustodiozup]

I could not replicate the issue, these are the steps I followed according to what I understood from the description

1 - Created in a payload.json file the component beagle:tExT

2 - At the configuration for my components I added an overwritten one beagle:TexT

3- The component was rendered correctly overwriting the default one