cbbackupmgr: Change order of restores so that FTS indexes are restored at end (per bucket)

See comments in CBSE-15404

Primarily a Capella request.

Change order of restores so that FTS indexes are restore after the data restore (per bucket).

This would mean that FTS /api/v1/bucket/<bucket_name>/restore is called after data has been restored for the bucket.

This change would be by default (i.e. there would be no new option introduced).

This change should be done after we have showfast tests with cbbackupmgr backup/restore with FTS indexes so that we can see what the impact of the change is.  Current thinking is that performance impact may be negligible since creating the FTS indexes after the data restore would make the data restore faster, so overall the restore time would be about time same despite the lack of concurrency (i.e. FTS index is not built at the same time as data restore).