devpool-issues.json should include all issues

[0x4007]

building new features like the notifications view would benefit greatly from the backend aggregating every issue in our network. Once they are in a single place, all operations can be handled instantly client side which is much better for UX compared to manually fetching each issue. In my case, every assigned issue.

---

Possibly should be posted as a separate task in command start stop:

At the same time the work.ubq.fi UI will likely need to be tweaked to only show what you can /start on

Ideally instead of just seeing if it's assigned, command-start-stop could have an API that can take the user auth, and take all the compiled issues from the whole network, and return a list of which they can /start.

It should check all prerequisite conditions like:

1. Are they already assigned to too many issues?
2. Is their XP sufficient?
3. Is it already assigned?
4. Were they previously disqualified from that task?
   Only then should it show on this view to the authenticated user.