[FR] Add delete_artifact method to mlflow API

[amesar]

Willingness to contribute

The MLflow Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature (either as an MLflow Plugin or an enhancement to the MLflow code base)?

• [ ] Yes. I can contribute this feature independently.
• [ x] Yes. I would be willing to contribute this feature with guidance from the MLflow community.
• [ ] No. I cannot contribute this feature at this time.

Proposal Summary

We need to add a mlflow.delete_artifact method to the API as an analog to mlflow.log_artifact.

Motivation

If clients can add an artifact they should be able to delete it.

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

Components

• [ x] 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: Local serving, model deployment tools, spark UDFs
• [ ] area/server-infra: MLflow server, JavaScript dev server
• [ ] area/tracking: Tracking Service, tracking client APIs, autologging