Introduce support for the most common features of Spring Security's @PreAuthorize

[geoand]

Docs will follow and be based on what @aureamunoz is already preparing

Relates to: #4037

[geoand]

@michalszynkiewicz can you please review the CDI related logic?

@gsmet would you like to go over the basics to see if I have missed anything obvious? I don't expect you to go over the actual code since it's quite involved :)

The good thing I think about this work is that there is a large amount of tests so all the features should be covered nicely.

[gsmet]

I added a few minor comment/questions.

Tests look good so it should be pretty safe.

[gsmet]

By the way, additional question: do you support precedence via parenthesis, IIRC, that's something we used in our conditions.

[geoand]

In this iteration there is precedence support I am afraid. I really wanted to get the basics out there and see what people think and then try to work out what people would like and use the most.
That said, if you have a good and easy way to deal with parentheses and precedence that doesn't require me to learn ANTLR, I'm all ears 😁.
Of course writing a proper parser will probably be necessary at some point...

[gsmet]

Couldn't we use an EL implementation somehow instead of doing dark magic? That would be taken care of I suppose.

That being said, I'm for merging this. But you can be sure you will need proper precedence support as that's very important for conditions.

I'm totally positive we used that in our applications at $previousJob.

[geoand]

I really don't want to pull in SpEL because who knows what it will take to get it working on native and how many classes it depends on.
I agree that we will definitely need proper precedence and similar features.
I'll ask @mkouba how he implemented those in Qute 😉

[gsmet]

@geoand I merged this one, thanks. I also merged @aureamunoz 's work on the Spring Security guide so you should be able to work on the documentation.

[gsmet]

BTW, will your parser fail if there are some precedence rules defined in an expression? I would rather have it fail than having it do incorrect things.

[geoand]

@gsmet Thanks!

Yes it will currently fail instead of providing incorrect results.

I will work on the documentation next week