fallback option in useClipboard

[Mister-Hope]

Clear and concise description of the problem

See #3008 (comment) and #3695

useClipboard use Clipboard API if possible, but there are chances that:

• The content is served in http like useClipBoard: after set "legacy: true", copy is not work in production env(http protocol is not work, https is work) #3695
• The permission API returned by browser is not standard (e.g.: with undefined or prompt, but still always refused to read and write when requesting for security)

Suggested solution

I am thinking whether adding a new option called fallback would be helpful, when this option is set, whenever Clipboard APi fails (user refuse when prompt or browser refused for security), try again using the legacy way.

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.