Upgrade to dynatrace-metric-utils 1.7.1

[jonatan-ivanov]

No description provided.

[jonatan-ivanov]

It seems the behavior changed, the build is failing if we upgrade (jonatan-ivanov@0626db3). This is probably because of a new behavior introduced in dynatrace-oss/dynatrace-metric-utils-java#29, see isDimensionValid

See the failure on the build scan: https://ge.micrometer.io/s/acijagpuypmjg/tests/overview?outcome=failed

org.opentest4j.AssertionFailedError:
    expected: "my.gauge,tag1=value1,dt.metrics.source=micrometer,tag2= gauge,1.23 1683566417583"
    but was: "my.gauge,tag1=value1,dt.metrics.source=micrometer gauge,1.23 1683566417583"

org.opentest4j.AssertionFailedError:
    expected: "my.counter,tag1=value1,dt.metrics.source=micrometer,tag2= count,delta=0.0 1683566417993"
    but was: "my.counter,tag1=value1,dt.metrics.source=micrometer count,delta=0.0 1683566417993"

[jonatan-ivanov]

According to @pirgeo, the Dynatrace V2 API behavior was changed to match this behavior so the users will see the same thing, we can fix our broken tests to match this behavior.

[pirgeo]

Thanks for taking care of this. The Dynatrace API behavior has not changed. The only difference is that empty dimension values are now dropped on the client side instead of being dropped on the server side. In theory, this would save a bit of network bandwidth if someone sent a lot of dimensions with empty values, but in practice, I think this is negligible.