Lexer issue when parsing hexadecimal literal

[LESdylan]

Norminette reports INVALID_SUFFIX on certain valid hexadecimal constants starting with 0xb or 0Xb also the version with capitalized letters

The error appears specifically when the hex literal contains:

• A capital letter B or lower case version following by a number
  you can see this pattern of error using this code for testing.

This is likely a lexer bug where certain letter+digit patterns are misinterpreted as a type suffix.

void	fn1(void)
{
	uint32_t	hex;

	hex = 0xb401D3;	// suffix invalid
	hex = 0xb123AB;	// suffix invalid
	hex = 0xbBEEFCA;
	hex = 0xb1b1b1;	// suffix invalid
	hex = 0xb00BAD;	// suffix invalid
	hex = 0xbADDAD;
	hex = 0xb0DEAD;	// suffix invalid
	hex = 0xb00000;
	hex = 0xb11000;
	hex = 0xb00FF0;	// suffix invalid
	hex = 0xbFFFFF;
	hex = 0xbABABA;
	hex = 0xb12345;
	hex = 0xb00001;
	hex = 0xbC0FFEE;
	hex = 0xb;
	hex = 0xb0;
	hex = 0xb00;
	hex = 0xb000;
	hex = 0xb401D3;	// suffix invalid
	hex = 0xbFFFFF;
	hex = 0xb1b1b1;	// suffix invalid
	hex = 0xb11000;
	hex = 0xb123AB;	// suffix invalid
	hex = 0xbEEFCA;
	hex = 0xa401D3;
	hex = 0xc401D3;
	hex = 0x1401D3;
}

[ef3d0c3e]

This is related to the incorrect regex used for parsing integer literals in norminette/lexer/lexer.py
The regex incorrectly detects the value type for literals, which leads to weird errors when using hexadecimals starting with 0xb

Here's a relevant regex101 that showcases the issue:
https://regex101.com/r/Ejx0V1/1

There is a workaround, which is to remove the invalid prefix detection part in the regex, but that means loosing the ability to detect invalid literal values. On the integer regex, if you remove the * in 0[bBxX]*, then the problem goes away.