Prevent loading unsupported claim attributes for Non-JDBC primary user stores

[PasinduYeshan]

Purpose

Currently, when a tenant is created, claim attribute mappings from claim-config.xml are saved to the database for the primary user store domain. When a new user store is added, the mappings from the primary user store domain are used unless the admin explicitly creates new attribute mappings.

With this PR, we aim to avoid potential conflicts arising from unsupported attributes in non-JDBC primary user stores. Specifically, if the primary user store is LDAP or another unsupported user store, new attributes that aren't natively supported should not be loaded. Admin should set these mappings manually, providing better stability and reducing errors.

Related Issues

• https://github.com/wso2/product-is/issues/19991

[PasinduYeshan]

This approach was changed due to a limitation in current implementation.