[FEATURE] Make lombok process jakarta.validation.NotNull and other jakarta null-prohibiting annotations as @NonNull

[Evemose]

Make lombok process jakarta.validation.NotNull and other jakarta null-prohibiting annotations as NonNull annotaion

Problem
Its common issue for developers working with validation annotations in jakarta/javax packages to have to duplicate nullity annotations, which leads to potential inconsistencies due to unneccesary code duplication.

Solution
Treat annotations that prohibit null values by specification same as NonNull annotaion

Target audience
Vast majority of web developers deal with jakarta validation annotations. Server side development is a most common use of Java, so feature would be helpful for virtually every Java developer.

Potential issues
Neccesity to keep track of jakarta specification updates and custom annotations from validation providers like Hibernate

Context
If lombok team would approve such feature, I could implement it myself, but I would like to know if maintainers of project think whether it would be expedient or not.