[sys-4729] ignore table handler loading error when apply replication log record

[seckcoder]

When follower applies kManifestWrite with newly added sst files, it also loads the table handlers and reads the footer blocks. If that fails due to leaf being overloaded, due to paranoid check, the shards will be errored permanently. Instead of erroring shards, it's actually safe to ignore the errors. But we still want to keep the paranoid checks, so adding a new parameter: ignore_table_load_error to VersionSet::LogAndApply function. If that's true, we force ignoring table handler loading error even if paranoid check is enabled.

[seckcoder]

Igor reminded me that we ran with max_open_files=-1, so we can't ignore the error here since we make the assumption that meta->fd.table_reader is always non-null