Add relative option for replace-text-component migration

[sam-b-rose]

WHY are these changes introduced?

We'd like to run component migrations on polaris-react which uses relative component imports.

WHAT is this pull request doing?

This adds the ability to run the replace-text-component migration on relative paths:

- import {DisplayText} from "../../DisplayText";
+ import {Text} from "../../Text"

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

[laurkim]

Tested locally and this is fantastic!! 💯 🚀

[laurkim]

Took another look and realized the display text mapping needs to be updated and the PR that the migration is run against also needs to be updated so that DisplayText maps to the correct Text variant.

DisplayText variant mapping updated

[laurkim]

/snapit

[github-actions]

🫰✨ Thanks @laurkim! Your snapshots have been published to npm.

Test the snapshots by updating your package.json with the newly published versions:

yarn add @shopify/[email protected]

yarn add @shopify/[email protected]

[laurkim]

/snapit

[github-actions]

🫰✨ Thanks @laurkim! Your snapshots have been published to npm.

Test the snapshots by updating your package.json with the newly published versions:

yarn add @shopify/[email protected]

yarn add @shopify/[email protected]