chore: Use Node 18

[jeremyckahn]

What this PR does

This PR eliminates the warnings produced by GitHub Actions about use of deprecated APIs:

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/[email protected], actions/setup-node@v1

The save-state command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The solution for this was ultimately to upgrade the GitHub Actions we're using. In trying to resolve this, I updated a number of things that turned out not to be necessary, but are worth doing regardless. Rather than roll them back, this is a good opportunity to update some of our aging project infrastructure. As such, this PR includes:

• Upgrading to Node 18
  • Required enabling --openssl-legacy-provider where necessary
• Upgrading to node-sass 8
• Replacing our scattered npm ci flags with an .npmrc file
• Light updates to our use of Material UI to avoid new deprecation warnings

How this change can be validated

Run npm ci locally, install Node 18 and make sure the important scripts work (test, start, build, and maybe spot-check a few others).

Additional information

I will have to update our Vercel configuration with similar settings once this is merged.

[vercel]

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

Name	Status	Preview	Updated
farmhand	✅ Ready (Inspect)	Visit Preview	Dec 30, 2022 at 3:57PM (UTC)

[jeremyckahn]

This is the only meaningful change in this file.

[lstebner]

everything seems to be working for me except tests. i tried completely removing node_modules/ and re-installing but all the tests fail with an issue in the setup file.

    Cannot find module '/Users/lukestebner/Sites/farmhand/node_modules/babel-preset-react-app/node_modules/@babel/runtime/helpers/interopRequireDefault' from 'src/setupTests.js'

      1 | import '@testing-library/jest-dom'
      2 | import 'jest-extended'
    > 3 | import Adapter from 'enzyme-adapter-react-16'
        |                              ^
      4 | import { configure } from 'enzyme'
      5 |
      6 | configure({

      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:306:11)
      at Object.<anonymous> (src/setupTests.js:3:30)

it doesn't seem to be an issue in github CI, but i can't seem to get past it on my machine. build, start, and the ci command all seem to be running as expected though

[lstebner]

test failures was my fault! looks good to me 😄