Remove IDs from octavia-CR

related issue: #525

The octavia-operator now create the required security-group and keypair by itself, because these must be in context of the octavia-user, so it can only be created after the initial run of the operator. To avoid these manual steps and an additional update of the CR, the operation does this now and creates the new security-group with its required rules and a public-private-keypair for the new octavia-user.

The other IDs of the flavor, image-owner and load-balancer-provider-network are now stored as kubernetes-secret and mounted as secret-injection-layer into the octavia-configs to configure them after the initial rollout without the need to modify the octavia-CR a section time.

Also updated the version of the mariadb of the octavia-operator.

Tests of the new resources are done by the intregration-tests instead of unit-tests, because it would required too much mocking of the openstack-api and integration-tests make sure, that the openstack-api also respond correctly.