[Remote Compaction] Parse options from OPTIONS file instead of using CompactionServiceInput

[jaykorean]

Summary

We've been serializing and deserializing DBOptions and CFOptions (and other CF into) as part of CompactionServiceInput. These are all readily available in the OPTIONS file and the remote worker can read the OPTIONS file to obtain the same information. This helps reducing the size of payload significantly.

The only downside of this approach is that if fail_if_options_file_error is false, we cannot safely guarantee that OPTIONS file is up-to-date with DB's current state. fail_if_options_file_error option is marked for deprecation. We will consider fail_if_options_file_error=false with remote compaction as incompatible features.

This also solves the problem where we had to open the default CF with the CFOption from another CF if the remote compaction is for a non-default column family. (TODO comment in /db_impl_secondary.cc)

Test Plan

Unit Tests

./compaction_service_test

./compaction_job_test

Also tested with Meta's internal Offload Infra