Remove deprecated block-based filter

[pdillinger]

Summary: In #9535, release 7.0, we hid the old block-based filter from being created using
the public API, because of its inefficiency. Although we normally maintain read compatibility
on old DBs forever, filters are not required for reading a DB, only for optimizing read
performance. Thus, it should be acceptable to remove this code and the substantial
maintenance burden it carries as useful features are developed and validated (such
as user timestamp).

This change completely removes the code for reading and writing the old block-based
filters, net removing about 1370 lines of code no longer needed. Options removed from
testing / benchmarking tools. The prior existence is only evident in a couple of places:

• CacheEntryRole::kDeprecatedFilterBlock - We can update this public API enum in
  a major release to minimize source code incompatibilities.
• A warning is logged when an old table file is opened that used the old block-based
  filter. This is provided as a courtesy, and would be a pain to unit test, so manual testing
  should suffice. Unfortunately, sst_dump does not tell you whether a file uses
  block-based filter, and the structure of the code makes it very difficult to fix.
• To detect that case, kObsoleteFilterBlockPrefix (renamed from kFilterBlockPrefix)
  for metaindex is maintained (for now).

Other notes:

• In some cases where numbers are associated with filter configurations, we have had to
  update the assigned numbers so that they all correspond to something that exists.
• Fixed potential stat counting bug by assuming filter_checked = false for cases
  like filter == nullptr rather than assuming filter_checked = true
• Removed obsolete block_offset and prefix_extractor parameters from several
  functions.
• Removed some unnecessary checks if (!table_prefix_extractor() && !prefix_extractor)
  because the caller guarantees the prefix extractor exists and is compatible

Test Plan: tests updated, manually test new warning in LOG using base version to
generate a DB

[facebook-github-bot]

@pdillinger has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[riversand963]

Didn't check in detail, but removing deprecated functionality which is already inaccessible in public API should be safe, assuming we have exercised good coding conventions so that all necessary changes are caught by compiler and tests.