Update set-up-sso-saml-2.0.md (#4057)

Removed unnecessary Okta/SAML user attribute formatting

## What are you changing in this pull request and why?
<!---
Describe your changes and why you're making them. If linked to an open
issue or a pull request on dbt Core, then link to them here! 

To learn more about the writing conventions used in the dbt Labs docs,
see the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md).
-->

## Checklist
<!--
Uncomment if you're publishing docs for a prerelease version of dbt
(delete if not applicable):
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
-->
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):
- [ ] Add page to `website/sidebars.js`
- [ ] Provide a unique filename for the new page

Removing or renaming existing pages (delete if not applicable):
- [ ] Remove page from `website/sidebars.js`
- [ ] Add an entry `website/static/_redirects`
- [ ] [Ran link
testing](https://github.com/dbt-labs/docs.getdbt.com#running-the-cypress-tests-locally)
to update the links that point to the deleted page

website/docs/docs/cloud/manage-access/set-up-sso-saml-2.0.md

@@ -56,9 +56,9 @@ Additionally, you may configure the IdP attributes passed from your identity pro
 
 | name | name format | value | description |
 | ---- | ----------- | ----- | ----------- |
-| email | Unspecified | ${user.email} | The user's email address |
-| first_name | Unspecified | ${user.first_name} | The user's first name |
-| last_name | Unspecified | ${user.last_name} | The user's last name |
+| email | Unspecified | user.email | The user's email address |
+| first_name | Unspecified | user.first_name | The user's first name |
+| last_name | Unspecified | user.last_name | The user's last name |
 
 dbt Cloud's [role-based access control](/docs/cloud/manage-access/about-user-access#role-based-access-control) relies
 on group mappings from the IdP to assign dbt Cloud users to dbt Cloud groups. To
@@ -154,9 +154,9 @@ dbt Cloud expects by using the Attribute Statements and Group Attribute Statemen
 
    | Name           | Name format | Value                | Description                |
    | -------------- | ----------- | -------------------- | -------------------------- |
-   | `email`        | Unspecified | `${user.email}`      | _The user's email address_ |
-   | `first_name`   | Unspecified | `${user.firstName}`  | _The user's first name_    |
-   | `last_name`    | Unspecified | `${user.lastName}`   | _The user's last name_     |
+   | `email`        | Unspecified | `user.email`      | _The user's email address_ |
+   | `first_name`   | Unspecified | `user.firstName`  | _The user's first name_    |
+   | `last_name`    | Unspecified | `user.lastName`   | _The user's last name_     |
 
 4. The following table illustrates expected **Group Attribute Statements**: