D7 views don't honor tracker and issue following

Since this is the last remaining hurdle for #1560010: [META] Port issue following functionality to D7 I'm assigning to myself.

First step is #1829734: Expose tracker data to views -- and the other views maintainers are already all over that. ;) They're not so psyched about *always* replacing the core uid_touch handler with the tracker-based one (for reasons I totally understand and support). So, we'll still have to do something about that. But, it shouldn't be too hard to get this working properly once that patch lands in views core. Worst case is we just have our default views conditionally check if tracker is enabled, and if so, reference the other handlers ourselves (we do that in D6, anyway, so that more of the fields are pulled from the tracker2 tables to optimize the queries). Or, maybe I'll publish a trivially tiny contrib for using the tracker-based uid_touch handler for all uid_touch handlers. Or something. Anyway, progress is definitely underway...

Meanwhile, I have a tentative date with nnewton to discuss D7 issue views on Saturday @ BADCamp. Of course, he's sad that we didn't port to Search API and do everything with a solr backend. I agree. That's really sad. Anyway, I'll report here (or perhaps at #949372: Port issue views to Search API so we can have a performant backend) based on the results of that conversation.

Assuming #1829734: Expose tracker data to views is going to land soon (which seems likely), here are two possible patches to fix our default 'My issues' view to make it tracker-aware.

Option A explicitly swaps out the argument handler for the default view. Bigger and uglier patch. Re-introduces the weirdness from D6 where our default views have conditional code and can't be directly just re-exported. Otherwise, probably a safer change.

Option B does what tracker2 does in D6 contrib: uses hook_views_data_alter() to swap out the handler for the existing 'uid_touch' argument and filter. Trivial patch. Doesn't touch default views. Works fine.

I'm leaning towards B. Any objections?

Thanks,
-Derek

Yay: #1829734: Expose tracker data to views is now in Views 7.x-3.x.

Any objections to B?

Although we can fix this temporarily, we'll have to postpone this on #949372: Port issue views to Search API so we can have a performant backend and make sure it's still working after that. We'll need a whole different solution once that happens, and it might be more involved (e.g. making sure flag data can be included in the search api index of issues), especially since people aren't going to like lots of latency with this. Therefore, I just pushed the easiest version of this fix for now (B) but I'm upping the estimate on getting this working once #949372 is done to 2 days.

Note: For now, we'll have to push views 7.x-3.x-dev into bzr until 7.x-3.6 is out. However, Jenkins UI seems dead, so I can't do much of anything about that right now.