IntelliJ Code Inspection Updates

IntelliJ Code Inspection Updates

- Use Lombok where possible
- Removed unused (interface) methods
- Removed parameters where method was called with only 1 (always same) value.
    This lead to so manual refactoring, more specific method names etc.
    For data job read I logged some details to get over this as the implementation is currently on hold/blocked
- Use 'record' (instead of class) where possible
- Apply @serial annotation
- Fixed unused result from matcher.find() We used to catch exceptions instead which is very bad :-(
- Some unused constant/return values needed for consistency, used annotation to ignore thee warning
- Removed Enum private value that was identical to Enum itself
- Uncheck casting, just added annotation to prevent warning I think they are all safe because we know and control the model
- Use {} for logging instead on string concatenation
- Use <a></a> for links in Javadoc
- Added missed null-checks
- Manually updated groovy test classes that were affected by some of above
- Spelling and grammar, original about 200 errors
     using 'Id' (with uppercase) I was flagged as a grammar issue and I like the idea of consistently using 'id' lower case in descriptions
     most typos where actually fixed by adding some work to the dictionary like cmhandle, onap, etsi etc.
     about 10% were genuine errors which also 2 or 3 variables affected which I have corrected now
- Security
     flagged some (http) links with suppress as we cannot change them
     some dependency issues remaining, need to check with Ger, looks like correct early warning without need for any CIO job or other tools!
- CODE ANALYZER ON WHOLE PROJECT
      only 4 java updates! inserted 2 finals (1 reverted as it was needed for test!), removed unnecessary casting in 2 places
      incorrectly add = sing in a cert.properties file for socker which I reverted

Issue-ID: CPS-2941
Change-Id: I439237422b01d533ae1c9301cbfcedbebf922fd4
Signed-off-by: ToineSiebelink <toine.siebelink@est.tech>