Provide block display of project_issue_user_issues for dashboard

Seems generally useful. Not sure exactly what you envision, but it'd be great if it was done via views. Let me know if you need any help on this.

Cheers,
-Derek

Mostly looks good, but I ran into a few problems when I enabled this on a local test site:

A) Since you're reusing the project_issue_user_issues view, you're inheriting a bunch of relationships and filters from the default display that we don't need. This results in a needlessly complicated and expensive query.

B) Enabling this results in a bunch of notices from project_issue_preprocess_views_view_table() since that function assumes (perhaps incorrectly) that the results include the issue status and priority (to allow the table rows to have the right classes and be styled appropriately). You're including status in the query and then excluding it from the display, but we either need to do the same for priority or we need to fix project_issue_preprocess_views_view_table() to not assume both exist in every result.

This fixed 4.A. 4.B is still broken.

This fixes 4.B.

Committed #6 to project_issue HEAD.