fix: 🐛 Update poetry-update log file name for commit message

[Anselmoo]

Update script to use poetry-update.log instead of update.log for tracking dependencies.

All PR-Submissions:

---

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open
  Pull Requests for the same
  update/change?

New ✨✨ Feature-Submissions:

---

• Does your submission pass tests?
• Have you lint your code locally prior to submission? Fixed:
• This PR is for a new feature, not a bug fix.

Changes to ⚙️ Core-Features:

---

• Have you added an explanation of what your changes do and why you'd like
  us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?

Summary by Sourcery

Fix the log file name in the weekly poetry bot workflow to ensure the correct file is used for commit messages when tracking dependency updates.

Bug Fixes:

• Correct the log file name used in the commit message from update.log to poetry-update.log in the weekly poetry bot workflow.

[semanticdiff-com]

Review changes with SemanticDiff.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the weekly-poetry-bot workflow to use a more specific log file name for tracking dependency updates. The change replaces 'update.log' with 'poetry-update.log' in the commit message creation process.

File-Level Changes

Files	Changes
.github/workflows/weekly-poetry-bot.yml	Updated the log file name from 'update.log' to 'poetry-update.log' for tracking dependency updates
.github/workflows/weekly-poetry-bot.yml	Modified the echo message to reflect the use of 'poetry-update.log'

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sourcery-ai]

Hey @Anselmoo - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (416e0c5) to head (0608dd8).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1493   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           44        44           
  Lines         4467      4467           
=========================================
  Hits          4467      4467           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.