build!: drop node 10 from engines list, update typescript to 4.6.3

[ddelgrosso1]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

[generated-files-bot]

Warning: This pull request is touching the following templated files:

• .kokoro/continuous/node10/common.cfg - .kokoro files are templated and should be updated in synthtool
• .kokoro/continuous/node10/docs.cfg - .kokoro files are templated and should be updated in synthtool
• .kokoro/continuous/node10/lint.cfg - .kokoro files are templated and should be updated in synthtool
• .kokoro/continuous/node10/samples-test.cfg - .kokoro files are templated and should be updated in synthtool
• .kokoro/continuous/node10/system-test.cfg - .kokoro files are templated and should be updated in synthtool
• .kokoro/continuous/node10/test.cfg - .kokoro files are templated and should be updated in synthtool
• .kokoro/continuous/node8/common.cfg - .kokoro files are templated and should be updated in synthtool
• .kokoro/continuous/node8/test.cfg - .kokoro files are templated and should be updated in synthtool
• .github/workflows/ci.yaml - .github/workflows/ci.yaml (GitHub Actions) should be updated in synthtool

[ddelgrosso1]

There are a bunch of Kokoro files still referencing Node 8 and Node 10. Can these be safely updated?

[ddelgrosso1]

OwlBot seems upset that I touched this. Should I have left this alone?

[sofisl]

@ddelgrosso1, everything looks good here except that the post-processor doesn't seem to be picking up the new ci.yaml file. It should look like: node: [12, 14, 16] and the SRS file should be testing 12, 14, and 16, since we're dropping Node 10 now. I wonder if the force-push perhaps overwrote what the post-processor should have done, would you mind attempting to re-push to see if the postprocessor runs? You can also attempt to run the script that I wrote in a new branch if that doesn't work, should be the same changes you've already made.

[sofisl]

The other question I have is for @bcoe, should these be build! or feat!

[ddelgrosso1]

@sofisl the reason the post processor didn't run is because I work from my own fork. I always have to manually trigger it. I've updated the 2 .yml files you called out.