fix: go back to using root user in Dockerfile

[jmeridth]

Pull Request

Proposed Changes

We have to do this because we have no active way to change permissions to $GITHUB_OUTPUT to a specific user when running the container

Add trivy ignore to top of Dockerfile to pass linting

Readiness Checklist

Author/Contributor

• If documentation is needed for this change, has that been included in this pull request
• run make lint and fix any issues that you have introduced
• run make test and ensure you have test coverage for the lines you are introducing
• If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from @jeffrey-luszcz

Reviewer

• Label as either fix, documentation, enhancement, infrastructure, maintenance or breaking

[Copilot]

Pull Request Overview

This PR reverts the Dockerfile back to using the root user instead of a non-root user to resolve permission issues with $GITHUB_OUTPUT when running the container. The change removes the user creation and permission setup logic while adding a trivy ignore directive for security scanning.

Key Changes

• Removes non-root user creation and switches back to root user
• Adds trivy ignore directive to suppress security warnings about running as root
• Simplifies the Docker build process by removing user management steps

[Copilot]

The trivy ignore directive lacks a comment explaining why this security warning is being suppressed. Consider adding a comment like # Required: Running as root needed for GitHub Actions output permissions

Suggested change

	#trivy:ignore:AVD-DS-0002
	#trivy:ignore:AVD-DS-0002 # Required: Running as root needed for GitHub Actions output permissions

[Copilot]

Running the container as root user increases the attack surface. Consider documenting in the README or inline comments the specific permission issues with $GITHUB_OUTPUT that prevent using a non-root user, and any mitigations in place.