Build a "bug / feature deployment pipeline" view

[str4d]

We want a way to track the progress of deploying bugfixes and feature changes all the way through to the Zashi apps.

Proposal:

• Mark bugfix and feature issues that we want to track with the C-tracked-bug or C-tracked-feature label as appropriate.
• Mark release issues in each repository with the C-release label.
• In the process of deploying a bugfix or feature, ensure that we connect the release issues in the DAG back via some path to the bugfix and feature issues they contain.
• In the renderer:
  • Grab all issues with the C-tracked-bug or C-tracked-feature labels.
  • Attempt to find paths through the DAG from the bugfix / feature GitHub issue to a zashi-android and/or zashi-ios repo C-release issue.
  • Use the results of that search to render a table showing what issues exist, and for those that do whether they are open or closed.
  • Specifically in the case of changes that get deployed in hotfix releases of Rust crates, also look through the DAG to find the issue for the next breaking release of the Rust crates, and render a separate row for that. This is intended as a defensive measure to ensure that we don't push out a hotfix, and then forget to merge back to main for the next breaking change release.

This should give an at-a-glance view of what deployment work remains to be done. Example of how this could be rendered:

Type	Issue	Rust crate	Android SDK	Swift SDK	Zashi Android	Zashi iOS
🐞	✅ zcash/librustzcash#1583	✅ zcash_client_sqlite 0.12.2	✅ 2.2.5	✅ 2.2.6	✅ 1.2.1	✅ 1.2.2
🐞	✅ zcash/librustzcash#1596	🛑 zcash_client_sqlite 0.12.3	📥	📥	📥	📥
	⬆️	🛑 zcash_client_sqlite 0.13.0	📥	📥	📥	📥
F	✅ TEX addresses	✅ 0.12.0	📥	✅ 2.2.0	📥	✅ 1.1.4
F	✅ zcash/librustzcash#1579	🛑 zcash_primitives 0.20.0	📥	📥	📥	📥

The example row above for which every column is complete (✅) is there for illustration. In practice, it would not actually be rendered (or maybe would only be rendered for a view that includes "recently completed").