chore: update dependencies

[MaxFrank13]

This PR addresses some work to get the Skills MFE caught up on some dependency upgrades.

Covered in this PR

• Upgrade to Paragon v22 which includes upgrades to the Form.Autosuggest and Chip components
• Remove redux and react-redux packages — they are not being used
• Updates any packages prefixed with a ^ to the latest minor version
• Adds env.config.js to .gitignore as well as provides example config file to help set up Algolia

Form.Autosuggest

The Form.Autosuggest received mostly updates in the way it's implemented in the code. However, most of these changes were made to facilitate some a11y issues that required extra work from the consumer to get the UI to be accessible. It should be accessible out-of-the-box now.

To check it out for yourself:

• Pull down this branch
• Run npm ci && npm start
• Go to localhost:1992
• Test the Autosuggest components
• Make sure you can navigate through the form using only a keyboard

Chip

The Chip has received some UI updates that seem fine to me. The only downside is they look a little more "clickable" now than they did before. The Chip component can be clickable, but the way we are implementing them here is simply to display information.

[justinhynes]

LGTM, but had a nitpick.

You mentioned this was a mashup of maintenance and multiple tickets; APER-3298 & APER-3330. Preferably, even if they are tiny, I like these in separate commits. That way, if ONE of the commits has a problem, we don't to roll back everything. It also helps pinpoint a problematic change.

If the change is focused on one thing and explodes, it's much easier to triage and roll back. Just food for thought.

[MaxFrank13]

LGTM, but had a nitpick.

You mentioned this was a mashup of maintenance and multiple tickets; APER-3298 & APER-3330. Preferably, even if they are tiny, I like these in separate commits. That way, if ONE of the commits has a problem, we don't to roll back everything. It also helps pinpoint a problematic change.

If the change is focused on one thing and explodes, it's much easier to triage and roll back. Just food for thought.

Great point! My thinking here was that one of the tickets was just to remove redux and react-redux (APER-3298) which I was very confident we weren't using at all in this repo. The only update that required refactoring was the Paragon upgrade (APER-3330). But even then, your point still stands. Having small commits is better. I'll be sure to do that next time or if this one blows up, I'll revert everything and then increment the changes gradually.