exchange: add option to disable pulling after cloning from clonebundle
Adds an option to not pull after downloading a clonebundle,as a workaround for an issue we sporadically notice:
For example:
- we have a bundle built at revision a
- we pull using clonebundle rev-a
- revision b is pushed
- after unpacking the clonebundle, a pull is done which does not find any new changes:
finished applying clone bundle
remote: obsolete feature not enabled but 23 markers found!
searching for changes
no changes found
- then it fails:
remote: abort: 00changelog@<rev-b>: no node