feat: runbooks queried from GitHub and Gitlab

[Mubashirshariq]

Closes #1780
/claim #1780

📑 Description

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

[vercel]

@Mubashirshariq is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[Matvey-Kuk]

I didn’t fully understand this part. Could you provide more context on how we are currently linking or associating the runbook with the incident?

I quite don't understand the question. The linking between incident and a runbook is expected to be added by this PR. There is many-many link expected. If I as a user link runbook to the incident, I expect to see the link from the incident page side as well.

[rajesh-jonnalagadda]

I didn’t fully understand this part. Could you provide more context on how we are currently linking or associating the runbook with the incident?

I quite don't understand the question. The linking between incident and a runbook is expected to be added by this PR. There is many-many link expected. If I as a user link runbook to the incident, I expect to see the link from the incident page side as well.

you mean this functionality for runbook too.

[rajesh-jonnalagadda]

I didn’t fully understand this part. Could you provide more context on how we are currently linking or associating the runbook with the incident?

I quite don't understand the question. The linking between incident and a runbook is expected to be added by this PR. There is many-many link expected. If I as a user link runbook to the incident, I expect to see the link from the incident page side as well.

you mean this functionality for runbook too.

^^

[rajesh-jonnalagadda]

I didn’t fully understand this part. Could you provide more context on how we are currently linking or associating the runbook with the incident?

I quite don't understand the question. The linking between incident and a runbook is expected to be added by this PR. There is many-many link expected. If I as a user link runbook to the incident, I expect to see the link from the incident page side as well.

you mean this functionality for runbook too.

@Matvey-Kuk ^^

[Mubashirshariq]

I didn’t fully understand this part. Could you provide more context on how we are currently linking or associating the runbook with the incident?

I quite don't understand the question. The linking between incident and a runbook is expected to be added by this PR. There is many-many link expected. If I as a user link runbook to the incident, I expect to see the link from the incident page side as well.

you mean this functionality for runbook too.

@Matvey-Kuk
All the other things are done only thing that is pending is incident one could you please provide some clarifications regarding this

Screen.Recording.2024-10-29.at.2.38.43.PM.mov

[Matvey-Kuk]

@Mubashirshariq thank you for the contribution! The core of the codebase is at good quality, but the UI and some UX decisions confuse me. I'm going to close the PR and proceed with the bounty payment via your GH sponsorship. @VladimirFilonov will take your codebase and continue working on it in order to bring it up to the UX standards we have.

[Matvey-Kuk]