Notice of some bugs either from HAL Core or vanilla grbl

[SienciLabs]

Done my best to look through the outstanding issues and thing these are unique contributions, if not, feel free to let me know. It's also possible some bugs have already been addressed or only exist on my SLB setup:

• $484 unable to be changed / set to =0
• Changing steps per mm values result in the next jog movement to reference the coordinate system as it was before the step/mm changed($100-$103)
• 'Keep homed status on reset' doesn't seem to do anything
• The only way to home any axis independently is to add it to the master homing cycle even if $22 'Allow manual' is enabled
• Sometimes there's 'stickyness' using M104QX where you’re unable to switch back to the default spindle
• G3 movements in the XY direction appear to cause a ‘hang’ but not a crash. In some situations, small pauses or stutters are seen. In other situations the movement stops for 10+ seconds and does not appear to restart. Could have something to do with motion planner math?
• Overrides on shorter files won't take effect if the buffer is large enough to fit the whole file when run (I think this is similar to https://github.com/grblHAL/core/issues/118#issue-1151770987)
• Hard limits don't seem to turn off for rotary axes (this seems to be addressed in a new version as mentioned in https://github.com/grblHAL/core/issues/371#issuecomment-1725785181