Fix expiry timeout bug in LocalIntermediateDataManager

[kfaraz]

Description

Fixes one of the bugs reported in #12692

As observed in this comment,
the expiry timeout is compared against the current time but the condition is reversed.
This means that as soon as a supervisor finishes, it gets cleaned up, irrespective of the specified
intermediaryPartitionTimeout period.

Changes

• Fix the condition
• Add tests to verify the new correct behaviour
• Reduce the default expiry timeout from P1D to PT5M
  to retain current behaviour in case of default configs.

Upgrade effects

On upgrade,

1. Clusters that have overridden intermediaryPartitionCleanupPeriodSec
   but not intermediaryPartitionTimeout might notice intermediate data
   from completed supervisors lingering for up to 5 more minutes.
2. Clusters that have overridden intermediaryPartitionTimeout but not
   intermediaryPartitionCleanupPeriodSec might notice intermediate data
   lingering for up to the specified partition timeout duration (i.e. their partition
   timeout will now start getting honored).
3. Clusters that have not overridden these configs will not notice any change.

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[kfaraz]

Thanks for the review, @clintropolis !