chore(deps): add jq as a dependency

[christinaexyou]

Updates the Dockerfile to install jq.

Description

The TrustyAI migration scripts have a dependency on jq.

Merge criteria:

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

Summary by CodeRabbit

• Chores
  • Added additional command-line tooling to the runtime environment (includes jq).
  • Updated Docker runtime configuration to improve container utility; no public API or UI changes.

[coderabbitai]

Warning

Rate limit exceeded

@christinaexyou has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minutes and 29 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

The Dockerfile runtime stage was modified to install the jq package via yum alongside existing utilities.

Changes

Cohort / File(s)	Summary
Dockerfile Updates Dockerfile	Added jq to the yum package installation list in the runtime stage.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰
I hopped into Docker’s stew,
Added jq to slices of brew,
Parsing bits with a happy prance,
Small change, big cheer — let’s dance!

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main change: adding jq as a dependency to the Dockerfile for TrustyAI migration scripts.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@Dockerfile`:
- Line 1: The Dockerfile has a stray leading character in the first line ("a#
Build stage - use native platform for builder to avoid emulation") which breaks
parsing; remove the leading "a" so the line begins with "#" (i.e., "# Build
stage - use native platform for builder to avoid emulation") ensuring the file
starts with a valid comment/instruction and the Docker build/Hadolint DL1000
error is resolved.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Stray a character breaks the Dockerfile build.

Hadolint reports DL1000: unexpected 'a' on this line. The leading a before # makes this neither a valid comment nor a valid Dockerfile instruction, so docker build will fail.

🐛 Proposed fix

-a# Build stage - use native platform for builder to avoid emulation
+# Build stage - use native platform for builder to avoid emulation

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	a# Build stage - use native platform for builder to avoid emulation
	# Build stage - use native platform for builder to avoid emulation

🧰 Tools

🪛 Hadolint (2.14.0)

[error] 1-1: unexpected 'a'
expecting '#', ADD, ARG, CMD, COPY, ENTRYPOINT, ENV, EXPOSE, FROM, HEALTHCHECK, LABEL, MAINTAINER, ONBUILD, RUN, SHELL, STOPSIGNAL, USER, VOLUME, WORKDIR, a pragma, end of input, or whitespaces

(DL1000)

🤖 Prompt for AI Agents

In `@Dockerfile` at line 1, The Dockerfile has a stray leading character in the
first line ("a# Build stage - use native platform for builder to avoid
emulation") which breaks parsing; remove the leading "a" so the line begins with
"#" (i.e., "# Build stage - use native platform for builder to avoid emulation")
ensuring the file starts with a valid comment/instruction and the Docker
build/Hadolint DL1000 error is resolved.

[lburgazzoli]

@christinaexyou can you rebase ?