container should use a known version of blueapi container to ensure compatibility with Helm chart

mx-bluesky-blueapi:1.5.0 contains blueapi 0.16 despite being based on the blueapi 0.10.1 image, as the dependencies for mx-bluesky pin blueapi>=0.11.0. Due to breaking changes in configuration in 0.12.0 and 0.15.0, this lack of consistent versioning gives an inconsistent and difficult to debug final product.

## Acceptance Criteria
- it is clearer which version of blueapi mx-bluesky depends on and is built into the container and the same version is used for the helm chart (if mx-bluesky versioned these containers with the version of blueapi, the only override required in the values of the helm chart is the `image.repository` and the image version would propagate from its current source for blueapi?)
- If possible, mx-bluesky pins to a specific version of blueapi and uses the same version as the base image
- mx-bluesky adopts new versions of blueapi Helm chart and container image regularly to ensure not falling behind new developments and features