Re-add deprecated typography docs

[laurkim]

WHY are these changes introduced?

Re-adds the deprecated typography docs and images on the style guide so that users can still reference them.
The get-props script had to be updated to resolve build errors. It was failing since the component files no longer existed in polaris-react/src/components.

WHAT is this pull request doing?

• Re-add dep components images
• Re-add dep component pages
• Adds new deprecatedComponents array to the get-props file and if the parsed file matches any of the elements, return empty object
• If component status is deprecated, props table is not rendered on component page

How to 🎩

🖥 Local development instructions
🗒 General tophatting guidelines
📄 Changelog guidelines

Copy-paste this code in playground/Playground.tsx:

import React from 'react';
import {Page} from '../src';

export function Playground() {
  return (
    <Page title="Playground">
      {/* Add the code you want to test in here */}
    </Page>
  );
}

🎩 checklist

• Tested on mobile
• Tested on multiple browsers
• Tested for accessibility
• Updated the component's README.md with documentation changes
• Tophatted documentation changes in the style guide

[sam-b-rose]

I like that we provide the mappings to the new components. Should we also include props and usage information until v12 for those not ready to upgrade quite yet? Looks like GitHub Primer does this by moving the components to a deprecated folder for referencing the documentation, but not exporting from the latest version index.

Maybe this is out of scope for this change. But possibly something to consider for future deprecated components.

[laurkim]

I like that we provide the mappings to the new components. Should we also include props and usage information until v12 for those not ready to upgrade quite yet? Looks like GitHub Primer does this by moving the components to a deprecated folder for referencing the documentation, but not exporting from the latest version index.

Maybe this is out of scope for this change. But possibly something to consider for future deprecated components.

I think this is a valid point but may require a bigger refactor of the style guide and increase scope for this change by a significant amount. I'm going to merge this into the v11 branch but happy to continue to have this discussion 👍