bump fireconfig to v0.5.5

[ogorman89]

• [ X ] I certify that this PR does not contain any code that has been generated with GitHub Copilot or any other AI-based code generation tool, in accordance with this project's policies.

Description

bumps fireconfig from v0.5.4 -> v0.5.5

• updated fireconfig version to latests in pyproject.toml
• re-ran poetry lock to capture changes
• once merged, this should resolve https://github.com/acrlabs/simkube/security/dependabot/22

Testing done

• How did you test your changes? Automated testing
• Does this code require any new tests to be written? No

Additional info

Resolves acrl-204

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.34%. Comparing base (713ffeb) to head (d021739).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #202   +/-   ##
=======================================
  Coverage   75.34%   75.34%           
=======================================
  Files          58       58           
  Lines        3253     3253           
  Branches      160      160           
=======================================
  Hits         2451     2451           
  Misses        698      698           
  Partials      104      104           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[drmorr0]

minor nitpick: I try to follow conventional commits for simkube, and then I have some tooling to autogenerate a changelog based on the commit prefixes. Can you rename the commit message here to chore: bump fireconfig...

[drmorr0]

minor nitpick: I try to follow conventional commits for simkube, and then I have some tooling to autogenerate a changelog based on the commit prefixes. Can you rename the commit message here to chore: bump fireconfig...

Or I guess maybe build(deps) instead of chore, since that's what dependabot is using for its other stuff...

[ogorman89]

I just noticed the "Comment on the PR" workflow failed to run. I think its the same permissions issue for 3rd party workflows but I noted it in ACRL-205