fix[DO-NOT-MERGE]: Update icons to use Artsy Icons

[MrSltun]

This PR resolves MOPRAT-863

Description

This PR is a follow-up to artsy/icons#58
This PR removes icons that exist in Artsy Icons, and updates the using of these icons to be used from @artsy/icons

[artsy-peril]

	Fails
🚫	Hi there! 👋 We use conventional commit formatting which has not been detected in your PRs title. Refer to README#327 and Conventional Commits for PR/commit formatting guidelines.

@artsy/icons

Author: Unknown

Description: [@artsy/icons](https://github.com/artsy/icons) is the canonical source for icons used at Artsy, and serves as an automatic build pipeline for generating JSX representations of `.svg` sources that can easily be imported into React apps.

Homepage: http://npmjs.com/package/@artsy/icons

Created	over 2 years ago
Last Updated	about 1 hour ago
License	MIT
Maintainers	6
Releases	75

README

@artsy/icons

@artsy/icons is the canonical source for icons used at Artsy, and serves as an automatic build pipeline for generating JSX representations of .svg sources that can easily be imported into React apps.

You can view available icons here and click to copy the import path of the desired icon.

Meta

• State: production
• GitHub: https://github.com/artsy/icons
• CI/Deploys: CircleCi; merged PRs to artsy/icons#main are automatically deployed to NPM
• Docs: https://icons.artsy.net
• Point People: @dzucconi

Installation and Usage

yarn add @artsy/icons

And then later, import icons like so:

import ArtsyLogo from "@artsy/icons/ArtsyLogo"

const MyApp = () => {
  return <ArtsyLogo />
}

Alternatively, visit the docs and select individual icons, which will copy the import path to your clipboard.

Adding New Icons

We've setup the repo so that adding new icons and publishing to NPM is as automated as can be:

1. Clone the repo: git clone https://github.com/artsy/icons.git
2. Create a new branch: git checkout -b add-new-icon
3. Copy your new icon .svg file into the src folder (and follow pre-existing naming conventions! 🙏)
4. Push your branch up to GitHub and open a PR. This should automatically be tagged with a minor label indicating a new feature addition
5. Merge PR. This will automatically generate JSX components and publish to NPM, and additionally update the docs
6. Once published, a new comment will be added to the PR announcing the new version.

Development

yarn install
yarn build
yarn docs

New dependencies added: @artsy/icons.

Generated by 🚫 dangerJS against ece4428