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 Docker container to run as root user instead of a non-root user due to permission issues with writing to $GITHUB_OUTPUT. The change removes the non-root user setup that was previously implemented for security purposes.

• Removes non-root user creation and configuration from Dockerfile
• Adds trivy security scanner ignore directive for running as root user
• Simplifies the container setup by removing user switching logic

[Copilot]

Running containers as root user creates security risks. Consider implementing a solution to properly set permissions on $GITHUB_OUTPUT directory instead of reverting to root user. This could involve using initContainers, volume mounts with proper permissions, or GitHub Actions workflow adjustments.

[Copilot]

The PR description mentions permission issues with $GITHUB_OUTPUT, but there's no documentation in the code explaining why root user is required. Consider adding a comment explaining the specific permission constraint that necessitates running as root.