Investigate whether secondary filtering metadata should handle rollbacks of config.cache.chunks

When a secondary rolls back changes to config.cache, it keeps its in memory filtering metadata. That means that it could potentially have a filtering metadata version higher than what it actually has. I went through a few scenarios and it looks like it might not invalidate the promises with causal consistency or snapshot reads. A more detailed investigation should be made to decide whether we need to handle rollbacks and document in this ticket if we determined why it is safe to keep it that way.