feat: add acl resource literal and prefixed matching

[biggusdonzus]

For this feature instead of adding a field resourcePatternType that distinguishes between literal, prefixed and regex (the one used in Aiven ACLs) matching, I added the fields resourceLiteral and resourcePrefixed. I did this way because we already had resource matching splito into resourceRe and resourceRePattern (the later used for backreference regex), and it felt natural (and more backward compatible) adding the new matching in the same way.

In the authorization method, to select between the proper resource matcher, it is used the one who is not null (as was done before my PR). This is a bit fragile by itself, for this reason I added the method validate() to verify that exactly one of the four resource matchers is not null. The validation is called by the constructor and by the decode class AclJsonReader.java.

The literal prefix needed a bit of work for the wildcard match because the wildcard rule is defined like Topic:* or Group:*, etc and the prefix must match the one of the action that we are authorizing, so for example:

Rule	Action	Result
Topic:*	Topic:some-topic	true
Topic:*	Group:abcde	false
Group:*	Group:abcde	true

I didn't want to introduce some big refactor so I added the class ResourceLiteralWildcardMatcher.java to perform this operation, trying to keep it fast as possible.

[tvainika]

Seems there are conflicts with hidden flag. I'll look a bit more. Now spotted also some minor issues

[tvainika]

Some minor things found, but this new exception being thrown with in some cases from validate: I'm not sure what will happen with it. What do you think, is it safe and why?