Resource leak in DruidSegmentReader

[jihoonson]

Description

The Yielder should be closed when it's done.

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.
• added integration tests.
• been tested in a test Druid cluster.

[b-slim]

@jihoonson wondering how did you run into this ? is there a stack trace you can share ?

[jihoonson]

Hey @b-slim, thank you for the quick review. I was just lucky. I was looking at the codes around Yielder and found it's not closed in DruidSegmentReader.