Check generated code for sonar warnings on modifier ordering

Two beans classes (EventsDocument, NewsDocument) define properties with the keywords "private final static" instead of "private static final". Although it is a cosmetic update, to change that would prevent Sonar warnings. Some internal Essentials classes have the same ordering of these keywords.

Please improve and run a Sonar check on a archetype project with all Essentials features installed: are there more Sonar warnings we can kill? Maybe also in the Essentials and ESSCOM projects themselves.