AP Eclipse compatability

[Kas-tle]

Currently, the annotation processor is not compatabile with eclipse because eclipse will not recognize classes that do not exist in the proper filepath for their respective package.

This also ensures multiple configs with the same name would not collide in the event of multiple configs with the same name.

[gliscowo]

While I approve of the general goal of this PR, it does not at all follow the code style of the rest of this codebase. Namely, local variables should use var instead of explicit type and names must not use abbreviations unless absolutely necessary or commonly established.

Further, I'm not really comfortable with how this handles a package-less class. While those is certainly unlikely to ever actually encounter, they should be correctly handled nonetheless instead of simply prepending a leading period to the wrapper name. While fixing this I would also move this logic into the function where's being used - in my opinion there is little use in having it live hundreds of lines away in its own function when this is the only place it's used

[Dragon-Seeker]

@Kas-tle Any update to such PR at all or attempts to change such to resolve issues from @gliscowo?