Clone a run - Cloud and Local - SDK and CLI

[sebastian-quintero]

Description

Introduces functionality for cloning a run in cloud and local:

• SDK: new methods for interacting with the cloud module ➡️ cloud.Application.clone_run and cloud.Application.clone_run_with_result.
• SDK: new methods for interacting with the localmodule ➡️ local.Application.clone_run and local.Application.clone_run_with_result.
• CLI: new commands for cloning runs ➡️ nextmv cloud run clone and nextmv local run clone.

Deprecates some features. Largely, when run "metadata" is requested, it always comes back to the user as:

{
  "description": "",
  "id": "latest-6O8pEx1vg",
  "metadata": {
    "application_id": "2005",
    "application_instance_id": "latest",
    ...
  },
  "name": "",
  ...
}

It has always been confusing to get metadata and find metadata to be a nested field that is part of that object. In the SDK, the complete object has always been called RunInformation. Following this, I am proposing we move away from metadata methods in favor of information methods. These are the following features that are being deprecated:

• SDK: cloud.Application.run_metadata in favor of cloud.Application.run_information.
• SDK: local.Application.run_metadata in favor of local.Application.run_information.
• CLI: nextmv cloud run metadata in favor of nextmv cloud run information.
• CLI: nextmv local run metadata in favor of nextmv local run information.

Last but not least, missing information in the actual run metadata was completed, such as options, execution_class, and others...