[CMSDS-3687] Configure Figma Code Connect

[jack-ryan-nava-pbc]

Summary

Let's try this again.

Note: This is part one of a series of Pull Requests related to Figma Code Connect snippets. This first one establishes a baseline of changes that we need in place to support code connect snippets.

I've added the following:

1. Base React configuration for Figma Code connect
2. Simple NPM scripts to run Code Connect when first building a connection file via the CLI, then for publishing and unpublishing snippets
3. Exclude *.figma.tsx files from the build process.

Notable exclusions are:

1. We'll get Typescript warnings for our Figma files. I think we actually want that since type declarations are important.
2. Type checking will fail as a result if you don't properly handle the types in the Figma file. Duh.
3. We will possibly want a separate configuration file for our Web Components. I'll update the package.json commands as well.

How to test

1. Create a .env file at the top level of the directory and place the team access token for Figma in a key called: FIGMA_ACCESS_TOKEN
2. npm i
3. npm run connect:build
4. Go through the interactive procedure

Checklist

• Prefixed the PR title with the Jira ticket number as [CMSDS-####] Title or [NO-TICKET] if this is unticketed work.
• Selected appropriate Type (only one) label for this PR, if it is a breaking change, label should only be Type: Breaking
• Selected appropriate Impacts, multiple can be selected.
• Selected appropriate release milestone

[derek-cmsds]

LGTM