Rename Paid Label to Permitted

[0x4007]

The intent is to tag the issue (for filtering purposes) that a payment permit has already been generated for the issue. I'm honestly still not a fan of this approach at all but it seems that the team is skeptical about rate limit overhead. So for now we will leave this feature in.

We need to rename from Paid to Permitted because Paid is misleading.

          @Steveantor this `Paid` label is a feature that I'm not aware of. I disagree with this approach because @rndquu already implemented cross referencing permits with etherescan transactions to actually verify that the payment has been made. I presume that you are simply adding the label "Paid" when it writes the permit which is misleading, because it doesn't actually check that the payment was made. 

Originally posted by @pavlovcik in #158 (comment)

[0x4007]

@Steveantor https://github.com/ubiquity/bounty-bot/pull/226/files#r1162506793

[Steveantor]

Permit Authorized is too verbose, it's Paid in the sense that we've generated the permit aka Paid,
now it's the bounty hunter's responsibility to claim those when is up to them.

[seprintour]

/start

[ubiquibot]

@seprintour The time limit for this bounty is on Sun, 14 May 2023 19:50:18 GMT

Your currently set address is:
0x3623338046b101ecEc741De9C3594CC2176f39E5
please use /wallet 0x4FDE...BA18 if you want to update it.

[Steveantor]

/assign

It was still on the discussion

[0x4007]

It was still on the discussion

The conclusion I came to is simply renaming Paid to Permitted! Regardless, technically because there was a price set on this issue its up for grabs no matter the current state of the bounty (it is our responsibility to not set prices for incomplete bounties for example.)

Ideally I would like to remove this label all together but it seems like the team decided that it is not feasible to do due to rate limiting?

[ubiquibot]

[ CLAIM 50 DAI ]

0x3623338...76f39E5

[Draeieg]

we can use "Paid" the same way and "Claimed" when the hunter gets his money