Add support for table operations reported from OpenLineage

[collado-mike]

Some of the OpenLineage integrations can report table operations, such as

• Truncate
• Drop
• Rename

We should record these operations in Marquez and reflect the new state of the table after the operation has completed.

[pawel-big-lebowski]

Some thought on how to achieve this.

• Collecting table state change information. - Table state change is a custom facet within outputs section of OpenLineage events.
  • Add new column operation to dataset_versions table
  • Update marquez.db.OpenLineageDao#updateBaseMarquezModel and marquez.db.OpenLineageDao#upsertLineageDataset methods to store table operation when present.
• Exposing with API
  • Method marquez.api.DatasetResource#getDataset should be modified to contain optionally the latest table state change information.
• Presenting on Web UI
  • This information should be shown on the popup box with dataset info similarly to "Run duration" & "Run State"

@wslulciuc does it make sense to you?

TODO: how to reflect rename?

[collado-mike]

This makes sense to me.

As we discussed offline, a good approach to rename might be to add the original dataset as an input and the target dataset as an output, while also creating a new version of the original dataset with a drop operation. From the UI perspective, users might see the original dataset as no longer existing, while the lineage persists to the new table.