feat: show sync github issue button to bounty owner

[thelostone-mc]

Description

When funder creates an issue, we sync the issue with GitHub to populate details. Once an issue has been created successfully, we've got a cron which pulls data and syncs every 24 hours to ensure all updates made to GitHub issue are synced

Issue

Many a time, after creating an issue -> the funder decides to update the description but this gets reflected on the Gitcoin issue only when the cronjob runs the mgmt command.
This can be frustrating to the funder especially if a change needs to be ported asap.

Solution

Introduce a button Sync Issue on the bounty detail page which gets rendered only if you are the owner of the issue / the admin.
The funder/admin would be able to click on this and this would pull the latest and update the DB thus allowing an immediate sync

The button is to be added next to the other action buttons aka the black rectangle in the below screenshot

NOTE

• Provide an action plan
• Reach Contributing guidelines + Setup
• Ensure solution is tested + recording is added

Reported on community slack a couple of time !

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 0.4 ETH (88.48 USD @ $221.21/ETH) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $135,143.31 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Workers have applied to start work.

These users each claimed they can complete the work by 12 months from now.
Please review their action plans below:

1) acolytec3 has applied to start work (Funders only: approve worker | reject worker).

1. Add new button placement as pictured.
2. Connect up to back end dashboard utility methods that sync a bounty in the DB.

Is there any value in just having the sync run the sync_geth command and update all recent bounties or is that too much overhead?

Learn more on the Gitcoin Issue Details page.

[thelostone-mc]

@acolytec3 nope just for that specific bounty ! Every bounty would be an overhead that may mess things up !

[acolytec3]

@thelostone-mc Sorry but I'm going to pull out of this one. I can't get my local environment working for some reason and I've been banging my head on it for a while. Will let someone else take a shot at this one in the meanwhile.

[thelostone-mc]

Sure thing ! Thanks for the update mate ^_^

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 11 months, 3 weeks from now.
Please review their action plans below:

1) pierrickgt has been approved to start work.

In order to complete this issue, I'll add the Sync issue button to the app/assets/v2/js/pages/bounty_details.js file and will make sure to only display it if the user is the funder of the issue or an admin.
I'll also use the code from the fund form in order to sync the Github issue.
2) acolytec3 has been approved to start work.

Finally fixed my local dev environment issues. If this is still open:

1. Add the Sync Bounty button
2. Wire up a new route in urls.py that calls the sync_web3 dashboard utils methods to resync the bounty between Web3 and the DB.
   3) acolytec3 has been approved to start work.

Finally fixed my local dev environment issues. If this is still open:

1. Add the Sync Bounty button
2. Wire up a new route in urls.py that calls the sync_web3 dashboard utils methods to resync the bounty between Web3 and the DB.

Learn more on the Gitcoin Issue Details page.

[PierrickGT]

I've completed the bounty from this issue, here is the PR: #4899
I will submit my work once my PR is reviewed.

[acolytec3]

Not trying to be nitpicky here but who is approved to work on this bounty?　The bot says I was approved and I'd already started my PR (which is mostly done) when I noticed the other one submitted by @PierrickGT that's already been approved by @danlipert and @octavioamu. If his approach is preferred, that's fine but would like confirmation.

[PierrickGT]

Not trying to be nitpicky here but who is approved to work on this bounty?　The bot says I was approved and I'd already started my PR (which is mostly done) when I noticed the other one submitted by @PierrickGT that's already been approved by @danlipert and @octavioamu. If his approach is preferred, that's fine but would like confirmation.

Hi,
Looking at your previous message, I thought you stopped working on this issue and that's why I've decided to open a PR.
Sorry for the misunderstanding.

[acolytec3]

@PierrickGT - not a big deal, just want direction from the core devs before I do anything else. It's been a fruitful learning exercise for me if nothing else.

@thelostone-mc, @danlipert, @octavioamu, who gets this one?