For unsharded clustered collections, this will include:

Record Store

• removing the existing record
• inserting the updated record with the new RecordId (which will be generated by it's cluster key)

Index Catalog

• Record updates through the IndexCatalog class currently assume the RecordId of the pre and post image remains constant.
• Callers should provide the IndexCatalog's updateRecord with the old and new RecordId.
• The old RecordId will be used for removing the existing secondary index, the new RecordId for inserting the new one that matches the newly modified cluster key

This ticket can be split up into 2 commits
(1) clustered collections with no secondary indexes
(2) clustered collections with secondary indexes*