chore: Release v0.44.3

[MeltyBot]

Prepare MeltanoSDK v0.44.3 for release.

Checklist:

• Check that the right version is set in all the files.
• Groom the changelog for wording or missing entries.
• Merge this PR once everything looks good.

Release Draft

Summary by Sourcery

Prepare release v0.44.3.

Bug Fixes:

• Fix: Do not emit a warning needlessly when rest_method is not set in a stream class.

Chores:

• Bump version to 0.44.3.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR prepares the Meltano SDK v0.44.3 release by updating the version number across the project, including in the changelog, cookiecutter templates, issue templates, documentation, and pyproject.toml. It also includes a fix to prevent unnecessary warnings related to the rest_method in stream classes.

Flow diagram for version update process in v0.44.3 release

graph TD
    A[Start Release Process] --> B[Update Version Numbers]
    B --> C{Update Files}
    C --> D[CHANGELOG.md]
    C --> E[Cookiecutter Templates]
    C --> F[Issue Templates]
    C --> G[Documentation]
    C --> H[pyproject.toml]
    D --> I[Add v0.44.3 Entry]
    I --> J[Document Bug Fix #2870]
    E --> K[Update SDK Dependencies]
    K --> L[Update Testing Dependencies]
    H --> M[Update Version and Commitizen Config]
    M --> N[End Release Process]

Loading

File-Level Changes

Change	Details	Files
Update the version number to v0.44.3 in various files.	Update version in mapper template pyproject.toml. Update version in tap template pyproject.toml. Update version in target template pyproject.toml. Update version in bug issue template. Update version in documentation configuration. Update version in pyproject.toml.	cookiecutter/mapper-template/{{cookiecutter.mapper_id}}/pyproject.toml cookiecutter/tap-template/{{cookiecutter.tap_id}}/pyproject.toml cookiecutter/target-template/{{cookiecutter.target_id}}/pyproject.toml .github/ISSUE_TEMPLATE/bug.yml docs/conf.py pyproject.toml
Add changelog entry for v0.44.3, including a fix for unnecessary warnings related to rest_method.	Add version entry for v0.44.3. Add a fix for issue fix(taps): Do not emit a warning needlessly when rest_method is not set in a stream class #2870 regarding unnecessary warnings for rest_method.	CHANGELOG.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @MeltyBot - 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 and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.33%. Comparing base (61c1413) to head (8332b65).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2871      +/-   ##
==========================================
- Coverage   91.37%   91.33%   -0.04%     
==========================================
  Files          62       62              
  Lines        5203     5203              
  Branches      675      675              
==========================================
- Hits         4754     4752       -2     
- Misses        317      319       +2     
  Partials      132      132              

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

[codspeed-hq]

CodSpeed Performance Report

Merging #2871 will not alter performance

_{Comparing release/v0.44.3 (8332b65) with main (61c1413)}

Summary

✅ 7 untouched benchmarks