Re-organize project: type labels

[abdonrd]

After:

• Unify the Qiskit Digital projects under Qiskit organization #2363

---

Now we should re-organize the project: type labels.

Right now we have. And I propose the changes below each one.

• project: challenges
  • We can continue using it, since it is an internal project
• project: documentation
  • No issues. Should we remove it?
• project: qiskit.org
  • We can remove it and assume the issues at Qiskit/qiskit.org as their own
• project: textbook (old version)
  • No issues. Should we remove it?
  • Assume issues at qiskit-community/qiskit-textbook
• project: brand book
  • No issues. Should we remove it?
• project: events
  • Just one issue. Should we remove it?
• project: textbook beta
  • We can remove it and use the Qiskit/platypus repository
• project: web components
  • We can remove it and use the Qiskit/web-components repository

After this we could end with this:

• Qiskit/qiskit.org
  • project: challenges
  • With the issues that were in [project: qiskit.org]
• Qiskit/platypus
  • With the issues that were in [project: textbook beta]
• Qiskit/web-components
• Qiskit/gh-actions

[techtolentino]

@abdonrd - this is a nice refactor of our labels, overall 👏🏽

Notes on the following, in my opinion:

• project: documentation - I remember we discussed having a better way to start organizing our docs, but it seems like it's not gaining any traction. I guess until we arrive at a plan, we can remove it.

• project: brand book - I believe this'll be up to @JRussellHuffman

• project: textbook (old version) - this can assume issues at https://github.com/qiskit-community/qiskit-textbook

• project: events - I imagine we'll have some events work in the future, but since none of it is prioritized as of now, I'm ok w/ removing

thanks for all this organizing Abdon 💪🏽