add active lock reason to PR

[notauserx]

add active lock reason to PR.
Since every pull request is an issue and the lock and unlock are on the IIssuesClient, updates the docs to reflect the design.
Fixes #2248

[notauserx]

I have extracted the lock/unlock methods from IIssuesClient to a new ILockUnlockClient, which is available in both the IIssuesClient and IPullRequestClient, so both clients can use the ILockUnlockClient.

I need a review for this PR and any feedback. I have intentionally left out the refactoring on the Reactive project, I will get to that once I get a review.

[JonruAlveus]

Hi @notauserx, thanks for this contribution ♥️! What you’ve done looks great, there’s just a couple of points:

• Please check the pr for warnings raised during the build as we’re trying to keep the warnings to none if possible
• It looks like the build is failing, but I think you’ve got that covered by the upcoming Reactive changes
• If you have time (and the desire!), please could you add/update the readme md files in the root/docs folder and/or any related linqpad samples?

[notauserx]

Thanks @JonruAlveus for the feedback. I will also update the relevant readme and the linqpad samples in the PR.

[notauserx]

@JonruAlveus I have updated the docs in the Issues.md. I did not find any relevant linqpad samples to update. Please let me know what you think.

[JonruAlveus]

Super happy with everything you’ve done here, if you can fix up the warnings I’d be happy to approve for merge!

[JonruAlveus]

release_notes: Reworks how Locking and Unlocking works on Issues and adds Locking and Unlocking to Pull Requests