patch: adding ability to pass labels through to the services for query

[drew-viles]

Which problem is this PR solving?

As it stands, we can pass annotations down to the query service using spec.query.annotations but any labels reflected in the spec.query.labels field only get passed to the deployment. This feels like it may have just been an oversight and to be honest, it's something I actually need as I'm sure some others do.
For my purposes, I need to be able to filter services based on their labels and the labels need to be custom ones such as environment, service, region and more. A long story short, it's for application discovery when using Teleport. so I can ensure certain people can only see certain services.

Description of the changes

This change sets a new variable called labels which gets the original labels values of util.Labels(GetNameForQueryService(jaeger), "service-query", *jaeger)` set as the default.
It then checsk to see if any additional labels have been passed and merges them into the map.

How was this change tested?

• I've run make test to ensure my tests work as expected.
• I'm running it in my production server right now. I've built and image and pused it to my repo here. I've then used this image to launch the operator with and without custom labels and in both cases it has worked as expected.

With no custom label

With custom label

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[frzifus]

cc @rubenvp8510