ILM: fix `after` rendering to xcontent

[talevy]

we currently ignore the TimeValue string representation and use our own that forces it to be represented in seconds. This is not user friendly, since our time-scale is often way beyond seconds.

The offending code:

elasticsearch/x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/indexlifecycle/Phase.java

Line 131 in ba8d4eb

builder.field(AFTER_FIELD.getPreferredName(), after.seconds() + "s"); // Need a better way to get a parsable format out here

[elasticmachine]

Pinging @elastic/es-core-infra

[colings86]

I'll have a PR up for this shortly

[colings86]

@bmcconaghy This should be fixed shortly in #33304

[colings86]

This was fixed in #33304