Update README.md

[PawanMude]

Added Amplify Logo

Problem

Issue number, if available:

Changes

Corresponding docs PR, if applicable:

Validation

Checklist

• If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
• If this PR requires a change to the Project Architecture README, I have included that update in this PR.
• If this PR requires a docs update, I have linked to that docs PR above.
• If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[PawanMude]

Added Amplify Logo in the file.

[PawanMude]

@sobolk and @rtpascual ; can you please review this request?

[sobolk]

@josefaidt is this fine?

[josefaidt]

Hey @PawanMude thank you for taking the time to file this! Do you mind if we pivot to using one of the logo assets from the Amplify documentation site? There are a few different sizes available
https://docs.amplify.aws/assets/icon/favicon-purple-32x32.png
https://docs.amplify.aws/assets/icon/favicon-purple-64x64.png

You can see the other sizes here https://github.com/aws-amplify/docs/blob/main/public/assets/icon/favicon-purple-64x64.png

[changeset-bot]

⚠️ No Changeset found

Latest commit: 61b76e1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[PawanMude]

Hey @PawanMude thank you for taking the time to file this! Do you mind if we pivot to using one of the logo assets from the Amplify documentation site? There are a few different sizes available https://docs.amplify.aws/assets/icon/favicon-purple-32x32.png https://docs.amplify.aws/assets/icon/favicon-purple-64x64.png

You can see the other sizes here https://github.com/aws-amplify/docs/blob/main/public/assets/icon/favicon-purple-64x64.png

@josefaidt : I've been using AWS Amplify pretty much since day one of it's launch, and the orange logo just fits the AWS vibe. The blue one, though, gives off the feeling that ; someone at AWS is missing Azure :) Logo is like a national flag for the community - we don’t keep changing the colors just because there’s a shift in leadership across the legislative, executive, and judicial branches.

Sometimes we need to agree to disagree; so if change is the flavor, and if you still want me to update the logo, I'm fine going with the community.

[PawanMude]

@josefaidt can you please review updates?