Button "to" prop to use react router

[nick-at-work]

When using the Button component, the href prop causes full page loads. We could wrap each Button (~50 of them) with react-router Link components, or since this project already has react-router, we can add the Link here. That's what this PR proposes.

To avoid breaking changes this is done with a new to prop, which also mirrors the react-router Link prop. However, it may be possible to re-use the href if you were bold enough. Pages outside the purview of the router in use would cause full page loads. I think.

Additionally, yarn insisted on updating the lockfile, and I added missing dependencies that I encountered when trying to build locally: @babel/preset-typescript and webpack.

Before:

<Link to="accounts/settings">
  <Button
    iconPrefix="settings"
    aria-label="settings"
    size="sm"
    variant="secondary"
    tone="neutral"
  />
</Link>

After:

<Button
  as='a'
  to="accounts/settings"
  iconPrefix="settings"
  aria-label="settings"
  size="sm"
  variant="secondary"
  tone="neutral"
/>

What type of change is this?

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality

Completeness Checklist

• TESTS: My changes maintain the baseline required test coverage, as specified by code climate analysis.
• DOCS: All new component work is covered in that component's Overview docs.
• DOCS: All new component work is covered in a component Playground.
• DOCS: All new visual changes or options are covered under relevant components' VisualTests.
• My code has no linting or typescript compile warnings.
• My work is tied to a Github issue and satisfies the acceptance criteria (if applicable) of the corresponding issue.

Quality Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

UI Checklist

• I have conducted visual UAT on my changes/features.
• My solution works well on desktop, tablet, and mobile browsers.

[erichardson30]

Well...I tried to look at this but The diff you're trying to view is too large. We only load the first 3000 changed files. 😢

[nick-at-work]

Well...I tried to look at this but The diff you're trying to view is too large. We only load the first 3000 changed files. 😢

Yeah.... I couldn't build locally without the added deps... but I can just reset and apply the code change this is silly for a small PR.

[codeclimate]

Code Climate has analyzed commit 598af96 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 75.0% (95% is the threshold).

This pull request will bring the total coverage in the repository to 97.9%.

View more on Code Climate.

[erichardson30]

#yolo