Save and write out the stitched topology

as a plan we can execute from the saved rspec.
spacing

Seems like this is how argument annotations want to be formatted.
Don't do extra processing on the SCS's rspec

According to what the omni tool puts out, the result we get back from the
stitching compute service is already the correct full request rspec for us to
send the involved aggregates to ask for the right route.
Oops, nest reindent_xml() calls as intended
Try to create stitched slivers per plan rspec