Plugin Support for Allow / Deny Bitswap replication based on peerID and CID

[whiteowl3]

Checklist

• My issue is specific & actionable.
• I am not suggesting a protocol enhancement.
• I have searched on the issue tracker for my issue.

Description

Recommended for issue here: #8763 (comment)
ipfs/go-bitswap#549 adds allow/deny functionality to bitswap based on peerid and cid.
A plugin should expose this functionality in go-ipfs.

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[lidel]

Related: #8492 (comment)

[iand]

See #7653 and #9010 f plugin route is decided on rather than the rules approach