The Stadard nova dataplane service created by the dataplane operator today does not reference a configmap that allows an end user to pass custom config.

as a result, almost all deployments will need to define a custom nova dataplane service to do any customisation.

This can be avoided by updating the standard dataplane service to refernce an optional config map that will by default be empty and can be modifed by and end user.

this will allow simplifying the adoption and greenfiled deployment procedure as well as simplifying the ci jobs.

As part of this change we need to adapt the users of the custom nova service to use the standard one instead:

• install_yamls: https://github.com/openstack-k8s-operators/install_yamls/blob/d605de1e5f15775b7d55f42dde2a926f84b83678/scripts/gen-nova-custom-dataplane-service.sh#L28
• ci-framework: https://github.com/openstack-k8s-operators/ci-framework/blob/7981c986707e682c450cc719fdb1c8cae81ee8e3/roles/hci_prepare/templates/dpservice-nova-custom-ceph.yml.j2#L6
• architecture: https://github.com/openstack-k8s-operators/architecture/blob/2d5ab8192e13dcc7976895233cbed68848f8b5e9/dt/bgp/edpm/nodeset/nova_custom.yaml#L5 (there are multiple service defs in the rep like this)
• our customer documentation