Adding Ploopyco functions so Host State Control can be implemented for Ploopy Nano

[t4corun]

Addressed gap in Ploopy Nano where drag scroll and dpi cannot be accessed at the userspace level. User can now implement Host State Control in their keymap

Description

Extends on the current code base. Drag scroll variable and dpi cycling logic moved into functions so they can be called at the userspace level.

Types of Changes

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

Issues Fixed or Closed by This PR

N/A

Checklist

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

[t4corun]

Revised PR based on @obosob's Discord comment. Removed keyboard level Host State control. Leave it to the user to implement it at the keymap. Tested on my Ploopy Nano.

The previous commit still has the Host state control if that is still desired.

[drashna]

Revised PR based on obosob's Discord comment. Removed keyboard level Host State control. Leave it to the user to implement it at the keymap. Tested on my Ploopy Nano.

Agree with obosob. This is something best left implemented at the user level.

However the helper functions are a good idea and useful.

[t4corun]

Thanks, but credit to @obosob for the idea. I was originally trying to call the ploopyco DRAG_SCROLL from my other QMK boards and was struggling