Make resource logo sizing more consistent

[kenxu95]

Describe your changes and why you are making these changes

This has been bothering me for a while. Our logos have been uploaded in a very adhoc fashion, so the sizing is significantly off sometimes.

This PR:

1. Fixes a storybook bug with circular imports.
2. Adds a story that puts all our resource logos side by side, with padding=1 so we can easily visualize the logos side by side.
3. Uses the Spark-only logo instead of the wordy one.

I have the uploaded logo png files on my local filesystem. Once I merge this in, I'll update the public assets bucket with the updated ones on the next release.

This is what things used to look like:

The Redshift, S3, Lambda, MariaDB, and MySQL logos were sized way too small. After adjusting, we get the following (MySQL and MariaDB still seem a little small, but that's just what their logos look like)

I realize these all look bigger than the before, that's just cus my window size changed, just focus on the relative sizes.

Related issue number (if any)

ENG-2951

Loom demo (if any)

Checklist before requesting a review

• I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
• I have performed a self-review of my code.
• I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
• If this is a new feature, I have added unit tests and integration tests.
• I have run the integration tests locally and they are passing.
• I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
• All features on the UI continue to work correctly.
• Added one of the following CI labels:
  • run_integration_test: Runs integration tests
  • skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

[vsreekanti]

The mocks look good to me. Any idea what's going on with the crazy linter errors? If it's a known issue, I'm happy to approve this.

[agiron123]

logos look good to me size wise, but I'd like to see the name of the integrations at the bottom.

[agiron123]

If lint is still giving you trouble, you can try running on the file itself:

npx eslint ResourceLogoStory.stories.tsx --fix