Emiel/add type property to metrics

[emielver]

A customer has noticed that adding the type property to a .yaml file causes the metric sync to error out with the following message:

Schema violation in **.yaml: 
Additional properties are not allowed ('type' was unexpected)

Meanwhile, the yml they were trying to sync was gathered using the COPY YAML button on Eppo's UI, and the API is able to handle a type field. So here we introduce a type field to the schema, and make it an ENUM accepting only the values allowed currently when creating a new metric in the Eppo UI.

[MaloChevillotte]

Looks like your IDE reformatted eppo_metrics_sync/schema/eppo_metric_schema.json.
It is difficult to see the changes actually made to this file and hence to get all the changes from the PR.
Can you reformat this file so that changes are easy to read?

[emielver]

@MaloChevillotte
The actual changes in the eppo_metrics_sync/schema/eppo_metric_schema.json are shown here in the light green (lines 127-130 and L153). I think removing the formatting will be a bit tricky, will this suffice for now?

[MaloChevillotte]

@emielver I understand that it is annoying but if your IDE this problem will pop up every time you push a commit with a json file in it. The sooner we fix this, the better.
Can you try reverting commit 7676b9d with one commit and re-commiting afterwards with proper formatting?

[emielver]

@MaloChevillotte I did some rebasing magic and now it should be working with the appropriate commits