chore: PoC STT - fix dockerfile, add license

[gpaoloni]

Description

Checklist

• Corresponding issue has been opened
• New tests added
• Feature flags / configuration added

Other Related Issues

None

Verification steps

AFTER YOU MERGE

1. Cut a release tag using the GitHub workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

[gpaoloni]

@copilot In a new branch, branched from this one (and PR should be open against this one), please edit .github/workflows/hrm-speech-to-text-ecs-deploy.yml deploy action so that it:

• Asks for 3 radio buttons / checkboxes, one for each service (proxy, limina and pyannote).
• If the corresponding checkbox is not checked, the container build is skipped, and instead the task definition resuses the latest/live tagged one (already present in ECR repo).
• By default:
  • proxy is checked.
  • limina and pyannote are unchecked.

[Copilot]

@copilot In a new branch, branched from this one (and PR should be open against this one), please edit .github/workflows/hrm-speech-to-text-ecs-deploy.yml deploy action so that it:

• Asks for 3 rad...

Done in commit d05746f. The workflow now has three boolean checkboxes in the manual dispatch form:

• build_proxy — checked by default (true)
• build_limina — unchecked by default (false)
• build_pyannote — unchecked by default (false)

When a checkbox is unchecked, all build-related steps for that service are skipped (Private AI registry login, licence injection, HUGGINGFACE_TOKEN fetch, and the Docker build/push itself). The Generate output step still runs unconditionally and emits the latest-tagged ECR URI for that service, so the ECS task definition update always references a valid image.

The same three boolean inputs were added to workflow_call as well (with the same defaults) so callers can opt-in to rebuilding specific services programmatically.