Docker Image Name Inconsistency Between Make Build and Kubernetes Config for v23.3 Release

### Summary
When building a Docker image for the HammerDB-TPCC workload using the `make` command with the v23.3 release, the generated Docker image has a different name compared to the one specified in Kubernetes configuration files. This issue was not present in the v23.2 release.

The Kubernetes configuration file expects the image name to be: `tpcc-mysql8031-base:v23.3`, but the `make` build generates the Docker image name as: `mysql8031-base:v23.3`. This discrepancy has been observed across multiple workloads, including Fio, BertLarge-PyTorch, SmartScience, Video-Structure, CDN-NGINX, 3DHuman-Pose-Estimation, SpecCpu-2017, ResNet50-PyTorch, SPDK-NVMe-o-TCP, and Istio-Envoy.

### Workload Release Version
v23.3

### Configuration
- Setting: `PLATFORM=`
- Setting: `REGISTRY=`
- Setting: `RELEASE=:v23.3`
- Setting: `TIMEOUT=86400`
- Setting: `BACKEND=kubernetes`

### Issue
We are encountering an issue while attempting to build Docker images for the HammerDB-TPCC workload using the `make` command from the workload directory. The problem lies in the inconsistency between the Docker image name generated by `make` and the image name specified in our Kubernetes manifest files. In the case of v23.3 release, the Kubernetes config file expects the image name to be: `tpcc-mysql8031-base:v23.3`, while the `make` build process generates the Docker image name as: `mysql8031-base:v23.3`.

This inconsistency has also been identified across several other workloads, including Fio, BertLarge-PyTorch, SmartScience, Video-Structure, CDN-NGINX, 3DHuman-Pose-Estimation, SpecCpu-2017, ResNet50-PyTorch, SPDK-NVMe-o-TCP, and Istio-Envoy.

### Expected
The image name specified in the Kubernetes configuration file should match the Docker image name generated by the `make` build process: `tpcc-mysql8031-base:v23.3`.