fix: drag to re-arrange custom columns not working

[dsmmcken]

resolves: #1282

Broken by #1013. Can't use prop spreading with our Button component, added support for spreading.
Needs silverheels cherry-pick.

[mattrunyon]

Any reason to not allow prop spreading any unknown props to our button? There's probably just some specific event handler we don't explicitly add to our button that react beautiful dnd uses

[dsmmcken]

I thought in general it was frowned upon, given our eslint rule? I have no preference for how it should be fixed.

[codecov]

Codecov Report

Merging #1299 (77644ca) into main (a80c6fc) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1299   +/-   ##
=======================================
  Coverage   45.88%   45.89%           
=======================================
  Files         492      492           
  Lines       34362    34371    +9     
  Branches     8567     8566    -1     
=======================================
+ Hits        15768    15775    +7     
- Misses      18543    18545    +2     
  Partials       51       51           

Flag	Coverage Δ
unit	45.89% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
packages/components/src/Button.tsx	76.31% <ø> (ø)

... and 30 files with indirect coverage changes

[mattrunyon]

This is one of the exceptions to the rule I think. The button component has a bunch of extra HTML props that it can/should be able to accept (it should be a superset of the base button). So it would be silly to explicitly add every prop instead of spreading those we don't handle in some specific way