[Module Proposal]: `Container job hosted GitHub runner with automatic updates`

### Check for previous/existing GitHub issues/module proposals

- [x] I have checked for previous/existing GitHub issues/module proposals.

### Check this module doesn't already exist in the module indexes

- [x] I have checked for that this module doesn't already exist in the module indexes.

### Bicep or Terraform?

Bicep

### Module Classification?

Pattern Module

### Module Name

avm/ptn/github-runner-container

### Module Details

Hi!
Here at InterIKEA I have created a nice Bicep template for a Github self-hosted runner deployed as an Azure container job. There are many features you would expect from an enterprisy template. Possibly the nicest one is automatic daily rebuilds of the runner container image from the source dockerfile. Others include KEDA scaling, customizing the dockerfile / startup script, PEM/PAT auth, support for reusing existing Azure resources and finally a simple UI to support providing the template as a TemplateSpec.


So how does the update magic happen? The Bicep template uses deployment scripts to dynamically download ORAS and uses that tool to push the source dockerfile and startup script into the container registry. Next it schedules a container registry task to perform a build operation on the dockerfile in that registry (which is referenced using the oci:// context).

I was wondering if there is interest in adopting this template and provide it to the broader community.

Cheers, Wouter

### Do you want to be the owner of this module?

No

### Module Owner's GitHub Username (handle)

_No response_

### (Optional) Secondary Module Owner's GitHub Username (handle)

_No response_

Start by reviewing the proposal and its comment thread, then check the module indexes to confirm the proposed avm/ptn/github-runner-container name and scope. The issue describes a Bicep template using an Azure Container Job, deployment scripts, ORAS, a Dockerfile, a startup script, and a TemplateSpec; the work is complete only if maintainership and an accepted contribution path are established.

Written by the indexing model from the issue text.