Move frontend-specific make targets to frontend/Makefile

[mbarnes]

What this PR does

Before this PR:

Frontend-specifc make targets were defined in /Makefile on the repo's root dir.

After this PR:

Frontend-specific make targets are defined in /frontend/Makefile for better component encapsulation.

This also shortens the make target names to: image, deploy, undeploy, deploy-private, undeploy-private

Jira:
Link to demo recording:

Special notes for your reviewer

Uses a kludge to get the full git repo into the build container, since files can't be copied from outside of Docker's build context:

• Makefile: Run "git archive" from the repo's root dir, output the temporary archive file into the frontend directory

• Dockerfile: Extract the archive file into the build container

• Makefile: Delete the temporary archive file

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Deployment: The deployment process was considered and addressed if required
• Testing: New code requires new unit tests.
• Documentation: Is the documentation updated? Either in the doc located in focus area, in the README or in the code itself.
• Customers: Is this change affecting customers? Is the release plan considered?