Extract Modal and add tokens

[ArthurTriis1]

Signed-off-by: Arthur Andrade [email protected]

What's the purpose of this pull request?

• Extracts Modal component from RegionalizationModal
• Applies the new Add Theming's global tokens base.store#407 to Modal and RegionalizationModal: new scoped tokens linked to global ones.

How does it work?

Before	Now

Tokens applied for RegionalizationModal and Modal.

How to test it?

• Check the RegionalizationModal documentation in the preview
• Check the Modal documentation in the preview

Checklist

You may erase this after checking them all ;)

Changelog

• Added an entry in the CHANGELOG.md at the beginning of its due section. The latest version should comes first.
• Added the PR number with the PR link at the entry in the CHANGELOG.md. E.g., New items in the pull_request_template.md (#4)

PR Description

• Added a label according to the PR goal - Breaking change, Enhancement, Bug or Chore.
• Added the component, hook, or pathname in-between backticks (``) - If applicable. E.g., ComponentName component.
• Identified the function or parameter in the PR - If applicable. E.g., useWindowDimensions hook.

Documentation

• PR description
• Added to/Updated the Storybook - if applicable.
• For documentation changes, ping @ carolinamenezes, @ PedroAntunesCosta or @ Mariana-Caetano to review and update.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
gatsby-store-storybook	✅ Ready (Inspect)	Visit Preview	Jun 27, 2022 at 7:32PM (UTC)

[vtex-sites]

Preview is ready

This pull request generated a Preview

👀   Preview: https://sfj-d86753a--gatsby.preview.vtex.app
🔬   Go deeper by inspecting the Build Logs
📝   based on commit d86753a

[renatamottam]

Approving cuz it looks the same from NextJS.Store

[vtex-sites]

Lighthouse Reports

Here are the Lighthouse reports of this Pull Request

📝 Based on commit d86753a

Lighthouse Report by page
📎   /
📎   /apple-magic-mouse/p
📎   /office

[hellofanny]

Approving looks the same as on the next.js repo.

It is just missing an adjustment on the Use Cases section that will be addressed in another PR 😄