Resolving a conflicted auth_key

[Tryneus]

Currently, the vector_clock_conflict_issue_tracker_t only works on the cluster_semilattice_metadata, but this should be expanded to include auth_semilattice_metadata.

In addition, it appears that 'resolve auth' also isn't working, which sucks, but it should be possible to work around it with 'unset auth' and 'set auth'.

[coffeemug]

@Tryneus -- are you on this?

[Tryneus]

yes, working on this now, almost ready for review

[Tryneus]

Ok, this is up in review 641. The Web UI doesn't really like the auth_key issue because it expects a UUID for an object, even though we don't have one (I put in a nil uuid in the spot). It would be useful to have the web ui support resolving auth_key, but I don't think it's necessary for this issue. I'll open another for that.

[Tryneus]

Alright, this has been merged into next in commit 3fc7a37 and cherry-picked into v1.6.x in commit 9a2638b.