Fix icon and update logos and favicon

[sisp]

What changes are proposed in this pull request?

The two circular arrows in the MLflow icon do not have identical shape which I believe is unintended. The top-left arrow has an inner radius of ~7.5 whereas the bottom-right arrow has an inner radius of ~7.7.

This PR fixes the icon by making the bottom-right arrow a flipped copy of the top-left arrow. The logo is updated accordingly and all PNG images and the favicon are re-generated from the vector graphics.

Follow-up of #5529.

Does this PR change the documentation?

• No. You can skip the rest of this section.
• Yes. Make sure the changed pages / sections render correctly by following the steps below.

Release Notes

none

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/artifacts: Artifact stores and artifact logging
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages
• area/examples: Example code
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/projects: MLproject format, project running backends
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/server-infra: MLflow Tracking server backend
• area/tracking: Tracking Service, tracking client APIs, autologging

Interface

• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• area/windows: Windows support

Language

• language/r: R APIs and clients
• language/java: Java APIs and clients
• language/new: Proposals for new client languages

Integrations

• integrations/azure: Azure and Azure ML integrations
• integrations/sagemaker: SageMaker integrations
• integrations/databricks: Databricks integrations

How should the PR be classified in the release notes? Choose one:

• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

[harupy]

@sisp

Can we remove TM in the new image? or was this added on purpose?

[sisp]

No, the TM wasn't added on purpose. It's in the SVG logo and I simply exported a PNG version, that's why it was added. I've pushed a commit where it's removed again.

[sisp]

Ah, would you like the TM removed in the SVG logo, too? I merely committed the unmodified SVGs in #5529 and the TM was included there.

[harupy]

@sisp Thanks for the reply. We discussed whether the logo should include the TM. Let's add it. Sorry for the confusion.

[harupy]

LGTM once #5618 (comment) is addressed!

[sisp]

@harupy No worries, I've reverted the last commit, so the TM is included in the PNG again.

[harupy]

thanks!