Refactoring based on development guidelines

[m0mus]

No description provided.

[tomas-langer]

The following tasks are part of this issue ("Validate" means check and if not compliant, fix):

• Change builders that accept other builders to accept a supplier instead
• Change scope to "provided" where reasonable to have a cleaner dependency graph
• Fix bundle dependency in MP security (brings in too many third party libraries)
• Move SE bundles to a /bundles root module and change group ids accordingly
• Remove Google Login from security bundle (third party dependencies)
• Fix module names and package names in security/providers and security/abac (and validate other modules adhere to dev guidelines)
• Validate that config is expected to be on the node of the component, rather then on the root (e.g. for security, the config should be on a node that contains "providers")
• Validate naming convention of configuration keys used by components
• Fix inconsistencies in getter and setter names
• Validate we do not create instances using "new" and use factory methods
• Refactor factory method names (use create)
• Refactor config methods in builders (use config)
• Validate java module files are in each module
• Refactor unit tests to use Hamcrest assertions

[tomas-langer]

Fixed all issues spawned from this one.