Add workaround to allow Sesame to work without atomic interactions

[ollien]

Description

This is a small workaround for #11389. While I don't love it (as this ultimately just works around the root cause), the original PR that caused this bug seems to be a fix for RGB (#10491), which this board does not have. It also seems that some other keyboards (namely massdrop/alt and massdrop/ctrl) seem to have done similar, citing "matrix delay", which I can only assume is this same issue.

cc: @kb-elmo

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

• I don't know if I'd call it "fixed", but [Bug] Looks like 0.11.0 broke something for jj40 #11389 is certainly relevant

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[kb-elmo]

Thanks 😄

[fauxpark]

Since this issue likely affects most other V-USB boards, it might be better to generalise this a little more. I'm actually thinking even my Plaid-Pad may be affected, as I recall having to tweak the delays on my macros around this time...