Split out dependecies and policy from odlparent(-lite)

Our policy and its enforcement is tied up with dependency declarations in the odlparent/lite pom machinery, with no clear distinction drawn.

This makes it difficult to modify policy enforcement rules downstream, as some things Just Come With odlparent.

Create odlparent-dependencies, which will only contain dependencyManagement, pluginManagement sections.

Create odlparent-policy, which will contain a pluginManagement section with configuration and tuneables.

odlparent-lite should then inherit from odlparent-policy and contain appropriate policy trigger hooks.