Rename split packages (#7246)

[mandy-chessell]

Signed-off-by: Mandy Chessell [email protected]

Description

As described by @planetf1 in issue #7246, it is not good practice to have java classes from different modules contribute to the same Java package. This PR renames classes and packages in order to ensure java packages sit within one module.

The changes to the java classes also required updates in consuming code - hence the large number of changed files.

Related Issue(s)

#7246

Testing

Build, UT, FVT

Release Notes & Documentation

Purely internal

Additional notes

This fix is to enable the use of Java modules in release 4.0.

[planetf1]

Thanks for doing the change. I've not validated this captures all the conflicts - hopefully, based on the original issue description.

The current module 'poc' is up to date with main as of today (including framework change) but I think this is harder to merge as there'll be a lot of conflicts from both my renames (which were only ever a test to help get things working to understand the impact) as well as the two large commits here.

I think the next step is probably to discuss whether we are going ahead with module support at our f2f. I can show the poc, and we can make a decision (the module-info files can easily be removed). I'll then figure the best way to merge/rebuild the module info files - probably on top of the regular 4.0 base (which is also up to date)