fix: correct constraint usage in parser and lexer definitions

[rotkiv93]

After the refactoring changes made in #60 , introduced some regex errors, containing blanks spaces in the float number definitions and other minor errors

[rotkiv93]

I didnt actually check for changes in the lexer/parsers for the specific languages (js, java, python), maybe its worth checking those in this PR

[gravemalte]

@rotkiv93 Thanks for the changes. Yeah please, everything you spot, change it. I rewrote large part of the grammar, I knew I would miss some things. We need to catch them now.

[gravemalte]

Also, please be sure to test it with the https://github.com/Universal-Variability-Language/java-fm-metamodel/tree/main test suite

[jmhorcas]

An additional note:

The following regex about STRING was an old issue (issue #47 ) already fixed some months ago to allow using the dot '.' within String attributes.
STRING: '\''~[\r\n'.]+'\'';
In this new version the issue appears again because the dot it's not allowed anymore again.
The correct regex would be:
STRING: '\''~[\r\n']+'\'';

without the dot!!

Be careful because the following regex is correct as it is:

ID_NOT_STRICT: '"'~[\r\n".]+'"';

This one is correct.

In summary: do not allow dot inside ID for features, but allow dot inside String attributes.

[SundermannC]

Thanks a lot for your work and comments so far! I will merge this to a dedicated branch and resolve remaining issues there.