docs: added documentation for data mapping of SAML attributes

[deepakprabhakara]

Related Issue or Design Document

Checklist

• I have read the contributing guidelines and signed the CLA.
• I have referenced an issue containing the design document if my change introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security vulnerability.
  If this pull request addresses a security vulnerability,
  I confirm that I got approval (please contact [email protected]) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation within the code base (if appropriate).

Further comments

[CLAassistant]

All committers have signed the CLA.

[vinckr]

this looks great 🎉
I have a few small change requests for a bit cleaner style, let me know what you think

[vinckr]

Suggested change

	:::note
	Important: Ensure that the appropriate identity schema is created before mapping attributes. The email attribute is natively
	available in `claims.email`, everything else is nested under `claims.raw_claims`.
	:::
	:::warning
	Ensure that the appropriate identity schema is created before mapping attributes. The email attribute is natively
	available in `claims.email`, everything else is nested under `claims.raw_claims`.
	:::

If you want to emphasize the importance here I would recommend to use "warning" or "danger" admonition - best use those if something will break prod if you get it wrong

[vinckr]

Suggested change

	Example: Mapping `firstName` and `lastName` from the SAML Identity Provider to the Ory identity schema (traits)
	#### Example SAML data mapping
	Mapping `firstName` and `lastName` from the SAML Identity Provider to the Ory identity schema (traits).

imo a bit cleaner to use a dedicated headline here