Update SAML connection ProviderName config name

[AmshikaH]

Purpose

Update SAML connection ProviderName config name to "samlAuthnRequestProviderName".

Related Issues

• Add ProviderName attribute to outbound SAML authentication request messages product-is#21536

Related PRs

• Add SAML2 Outbound Request Attribute ProviderName UI #7225
• Update SAML connection ProviderName config name wso2-extensions/identity-outbound-auth-samlsso#183

Checklist

• e2e cypress tests locally verified. (for internal contributers)
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Relevant backend changes deployed and verified
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines
• Ran FindSecurityBugs plugin and verified report
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.04%. Comparing base (563925f) to head (9ecf97c).
Report is 7 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7302   +/-   ##
=======================================
  Coverage   36.04%   36.04%           
=======================================
  Files          42       42           
  Lines         899      899           
  Branches      217      205   -12     
=======================================
  Hits          324      324           
- Misses        529      575   +46     
+ Partials       46        0   -46     

Flag	Coverage Δ
@wso2is/core	36.04% <ø> (ø)

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

see 13 files with indirect coverage changes

incorrect changeset

[pavinduLakshan]

Changeset is accurate IMO, as in this case, we are renaming a configuration. Therefore connections feature (and also i18n module) should release this update as a major version I think. thoughts @brionmario ?

[brionmario]

Changeset is accurate IMO, as in this case, we are renaming a configuration. Therefore connections feature (and also i18n module) should release this update as a major version I think. thoughts @brionmario ?

Lets go with a minor version.
If this gets released as a major, then console also will be bumped as a major (not 100% sure of this and need to verify with the changesets config file).

We only do major releases in Console & My Account and other apps for product releases ex: IS 7.1.0

[wso2-jenkins-bot]

🦋 Changeset detected

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.