Move issue triage URL generation to an easier place to rapidly edit

[BigLep]

This concerns https://github.com/protocol/web3-dev-team/blob/main/notebooks/ecosystem-dashboard-url-generation-for-maintenance-triage.ipynb

The purpose of that notebook is to make it easy to generate ecosystem dashboard URLs for issue triage. The problems with it is that it ses Python and Jupyter notebooks. I assume most people don't have setup on their machine. The barrier to entry means that I just end going to make the changes vs. having triage owners make updates directly.

Ideally this could be hosted in some web-application so it's easy/self-service for anyone to make changes.

Ideas:

1. Use a hosted-Jupyter solution (e.g., Binder, Google Colab - I have no idea what the latest and greatest are these days)
2. Switch to something like Observable which PL already uses other places and leverages language (JS/TS) that more folks are familiar with?

This isn't required, but the usual workflow now is that I:

1. Generate new URLs
2. Copy/paste them into our weekly templates (https://www.notion.so/pl-strflt/js-ipfs-Issue-Triage-Notes-09c8e86b5d744c74a88c61da43899655#2f49b43cf9984428a6a58c0152be558f ).

It would be nice to have the whole template itself in the Observable notebook so could copy/paste that wholesale. That isn't required though.

[SgtPooki]

I think having this in an observable notebook is the least painful route. As some folks already know, I recently through together some javascript for generating both ecosystem-research links, and backup github links, for the GUI Triage: https://github.com/protocol/w3dt-stewards/tree/main/scripts/create-triage-links

That code might make it easier for us to migrate to observableHq, but steve's notebook seems like it handles quite a few more query params and customization of links.

[SgtPooki]

@BigLep would you prefer I open an issue for adding instructions for running/editing https://github.com/protocol/web3-dev-team/tree/main/notebooks, or that we focus on resolving the issue of running triage URL generation with less effort?

[BigLep]

@SgtPooki : if someone else wants to run the the Python notebooks, I can get details together on how I do it. That is less net work than switching to Observable. If someone has more time, getting switched to Observable would be great.

[SgtPooki]

I got it together by running

# Repo cloned at /Users/sgtpooki/code/work/protocol.ai/protocol/web3-dev-team
cd /Users/sgtpooki/code/work/protocol.ai/protocol/web3-dev-team/notebooks
asdf install python latest
asdf local python latest
echo "use asdf" > .direnv
direnv allow
pip install jupyterlab
python3 -m jupyterlab

[SgtPooki]

I would love to migrate us to observable. I will look into that if I get through some of my other action items. using the code I already added in https://github.com/protocol/w3dt-stewards/tree/main/scripts/create-triage-links should be trivial with observableHq