reftable: D/F conflicts done twice when writing refs

The reftable library performs D/F conflict checks twice when writing refs:

• Once via refs_verify_refname_available() in the reftable backend.
• And once in the reftable library.

This is a waste of compute given that the former should already reject all ref udpates which do create a D/F conflict.