LPS-48935 Don't copy the JUnit jar file to the app server
LPS-48935 Convert the portal-test module into a valid OSGi bundle and deploy it to the correct folder (not in the app server)
LPS-48935 Convert the portal-test module-internal into a valid OSGi bundle and deploy it to the correct folder (not in the app server)
LPS-48935 I matched portal-impl/bnd.bnd - not sure if that version # is correct, should be 7.0.0 no?
LPS-48831
LPS-48970
Revert "LPS-48929 Keep the logic in the module"

This reverts commit 6da2a217e5968e2e055bb561da9f39456317aa3b.
LPS-48929 SF
LPS-48971 - Set tomcat version number when testing bundles
LPS-48993 ConfigurationActions registered from OSGI don't dynamically cause a portlet to enable configuration UIs
LPS-48993 SF
LPS-45541 Merge should fail on this case
LPS-48965 Properly mock all input combinations
LPS-48919 Simplify
LPS-48919 Add unit tests
LPS-48919 Add DDMFormValuesToField converter
LPS-48994 add some missing features to osgi portlet support
LPS-48994 SF
LPS-48994 SF
LPS-48728 add repository registry core classes

The idea is to be able to register new repositories (each with different
sets of capabilities) at runtime. For that, people will need to implement
the RepositoryRegistryPlugin. The portal will call the registry plugin
to register a repository creator (the name RepositoryFactory was already
taken) and its capabilities.