Improve documentation clarity for tags variable and update type in function definition.

[vonpetersenn]

Summary:

• Clarified the expected structure and content of the tags variable in the documentation.

Changes:

• Initially changed the type declaration of tags in the first commit, which caused errors in the test.
• Reverted the type declaration to maintain consistency with the library's style.

Notes:

• The type declaration was omitted to avoid test errors and adhere to the existing style of the library.

[ablaom]

@pebeto Is this really the way this works?

[pebeto]

Hi @ablaom. Yes, tags must be a Vector of Dictionaries with key and value, as expected in mlflow (i.e. https://mlflow.org/docs/latest/rest-api.html?highlight=tags#experimenttag).

[pebeto]

Also is good to mention that I'm working on the next big change for this library (9fe5e9a), where I'm pairing everything with the last mlflow specification (including types).

[ablaom]

This just seems weird. If I want to assign the value "bar" to a tag called "foo", and a value "gala" to a tag called "missy", I would have expected to pass Dict("foo" => "bar", "missy" => "gala"). But my reading of the proposed doc clarification is different: I should pass [Dict("key" => "foo", "value" => "bar"), Dict("key" => "missy", "value" => "gala")] instead?

[vonpetersenn]

I also found it counterintuitive, which is why I opened the pull request.

[ablaom]

Right. Then I'll leave to @pebeto to finalise the review. Perhaps we can make this more intuitive at the next breaking release.

[ablaom]

@pebeto Do you have the possiblity to finish this review?