feat: Add schema alias for default_target_schema setting

[KaruturiS]

This PR adds the 'schema' alias to the default_target_schema setting in TARGET_SCHEMA_CONFIG. This allows users to use either key in their configuration, resolving issue #2766.

Summary by Sourcery

New Features:

• Allow configuring the default target schema using either the default_target_schema or schema key in TARGET_SCHEMA_CONFIG.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a new configuration alias so that the existing default_target_schema setting can also be specified as schema in TARGET_SCHEMA_CONFIG, improving configurability while maintaining backward compatibility.

Class diagram for updated TARGET_SCHEMA_CONFIG Property with schema alias

classDiagram
    class Property {
        +string name
        +string title
        +string description
        +ConfigType type
        +list~string~ aliases
    }

    class TargetSchemaConfig {
        +Property default_target_schema
    }

    TargetSchemaConfig --> Property : uses

    class DefaultTargetSchemaProperty {
        +name = default_target_schema
        +aliases = [schema]
        +title = Default_Target_Schema
        +description = Default_target_database_schema_name
    }

    DefaultTargetSchemaProperty --|> Property

Loading

File-Level Changes

Change	Details	Files
Allow the default_target_schema configuration property to be set using an additional schema alias key.	Extend the Property definition for default_target_schema to include an aliases=["schema"] parameter. Preserve existing behavior and validation of default_target_schema while adding support for the new alias key in configuration files.	singer_sdk/helpers/capabilities.py

Possibly linked issues

• bug: New setting alias schema for builtin default_target_schema #2766: PR adds aliases=["schema"] to default_target_schema, implementing the requested schema alias behavior from the issue.

---

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!

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 - I've reviewed your changes and they look great!

---

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.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 8 untouched benchmarks

---

_{Comparing KaruturiS:fix/schema-alias-issue-2766 (5048af9) with main (ec2cb65)}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.86%. Comparing base (ec2cb65) to head (5048af9).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3454   +/-   ##
=======================================
  Coverage   93.86%   93.86%           
=======================================
  Files          73       73           
  Lines        5946     5946           
  Branches      729      729           
=======================================
  Hits         5581     5581           
  Misses        271      271           
  Partials       94       94           

Flag	Coverage Δ
core	82.35% <100.00%> (ø)
end-to-end	75.27% <100.00%> (ø)
optional-components	42.80% <0.00%> (ø)

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

☔ 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.

[edgarrmondragon]

I'll defer this. I don't see a very strong need for this at the moment.