Features: useLinkClickHandler and useLinkPressHandler

[chaance]

This PR adds two new APIs that simplify the creation of custom Link components:

• useLinkClickHandler for react-router-dom
• useLinkPressHandler for react-router-native

The idea is the same for each. There is a lot of logic in our onClick handler for the DOM link, and this hook provides a simple wrapper that consumers can use to capture all of that logic while customizing other aspects of rendering.

import { useHref, useLinkClickHandler } from "react-router-dom";
import { styled } from "styled-components"; // could be whatever

const StyledLink = styled.a`
  color: fuschia;
`;

const Link = React.forwardRef(
  ({ onClick, replace = false, state, target, to, ...rest }, ref) => {
    let href = useHref(to);
    let handleClick = useLinkClickHandler(to, { replace, state, target });

    return (
      <StyledLink
        {...rest}
        href={href}
        onClick={event => {
          onClick?.(event);
          if (!event.defaultPrevented) {
            handleClick(event);
          }
        }}
        ref={ref}
        target={target}
      />
    );
  }
);

Though the internals of Link in react-router-native are much simpler, I added the hook there for feature parity between the two packages.

[hugmanrique]

This looks like a great replacement for the as/component prop, effectively moving react-router's state up the tree into user-defined components. This solves all concerns I had on #7598.