fix: update step names for Docker image builds in workflow

[Vamshi-Microsoft]

Purpose

This pull request updates the Docker build and push workflow to use more generic and consistent names for the Docker images. The main changes are renaming the image build steps to better reflect their actual roles in the system.

Image naming consistency improvements:

• Renamed the step from "Build and Push ContentProcessorAPI Docker image" to "Build and Push Backend API Docker image" to clarify the purpose of the backend API image.
• Renamed the step from "Build and Push ContentProcessor Docker image" to "Build and Push Processor Docker image" for better alignment with the service's function.
• Renamed the step from "Build and Push ContentProcessorWeb Docker image" to "Build and Push Frontend Docker image" to use a more standard naming convention for the frontend service.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[Copilot]

Pull request overview

This pull request updates the GitHub Actions Docker build/push workflow step display names to be more generic and consistent with the services they build (backend API, processor, frontend), without changing build behavior.

Changes:

• Renamed the backend API image step label to “Build and Push Backend API Docker image”.
• Renamed the processor image step label to “Build and Push Processor Docker image”.
• Renamed the frontend image step label to “Build and Push Frontend Docker image”.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.