view: fix use-after-move when handling view update failures
view: fix use-after-move when handling view update failures

The code was susceptible to use-after-move if both local
and remote updates were going to be sent.
The whole routine for sending view updates is now rewritten
to avoid use-after-move.

Refs #8830
Tests: unit(release),
       dtest(secondary_indexes_test.py:TestSecondaryIndexes.test_remove_node_during_index_build)

scylladb/scylla,scylladb/scylla,scylladb/scylla,scylladb/scylla