Clean up after add kill bufferPeriod

[kfaraz]

Follow up PR to #12599

That PR introduces some changes that can be simplified.

Changes

• Rename column used_flag_last_updated to used_status_last_updated
• Remove new CLI tool UpdateTables.
  • We already have a CreateTables with similar functionality, which should be able to handle update cases too.
  • Any user running the cluster for the first time should either just have druid.metadata.storage.connector.createTables enabled or run CreateTables which should create tables at the latest version.
  • For instance, the UpdateTables tool would be inadequate when a new metadata table has been added to Druid, and users would have to run CreateTables anyway.
• Remove upgrade-prep.md and include that info in metadata-init.md.
• Fix log messages to adhere to Druid style
• Use lambdas

---

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.
• a release note entry in the PR description.
• 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.

[jon-wei]

LGTM

[kfaraz]

Thanks for the review, @jon-wei !
Merging as failure in ITNestedQueryPushDownTest is unrelated.