fix: 💚 Update GitHub Actions workflow to use 'gh pr merge' command

[Anselmoo]

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

Update the GitHub Actions workflow to run more frequently for testing, enhance timestamp precision in branch names and commit messages, and adjust the pull request merge strategy to use the '--merge' option.

CI:

• Update GitHub Actions workflow to run every hour for testing purposes instead of every Sunday at midnight.
• Modify branch naming and commit messages to include hours and minutes for more precise timestamping.
• Change the GitHub CLI command to merge pull requests using the '--merge' option instead of '--rebase'.

[semanticdiff-com]

Review changes with SemanticDiff.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the GitHub Actions workflow for weekly dependency updates. It modifies the cron schedule, changes the branch naming convention, updates commit messages with more precise timestamps, and adjusts the PR creation and merging process.

File-Level Changes

Change	Details	Files
Modified the cron schedule for the workflow	Changed from running every Sunday at midnight to running every hour Added a comment indicating the change is for testing purposes	.github/workflows/weekly-poetry-bot.yml
Updated branch naming and commit message timestamps	Added minutes to the branch name for more uniqueness Updated commit messages to include minutes in the timestamp	.github/workflows/weekly-poetry-bot.yml
Modified the Pull Request creation and merging process	Updated PR title to include minutes in the timestamp Changed the PR merging step to use 'gh pr merge' command Switched from rebase to merge strategy for PR merging	.github/workflows/weekly-poetry-bot.yml

---

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 - here's some feedback:

Overall Comments:

• The cron schedule has been changed to run every hour for testing purposes. While this is useful for development, ensure this is changed back to a more appropriate frequency before merging to production to avoid unnecessary PR spam.
• The PR merging strategy has been changed from rebase to merge. Could you provide the rationale behind this change? Both strategies have their merits, so it would be helpful to understand the reasoning.

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 (ced5e88) to head (458fac0).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1528   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           44        44           
  Lines         4466      4466           
=========================================
  Hits          4466      4466           

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

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