Cell Range ctrl-c and ctr-v strange behavior when column bottomCalc option is added

[guidry]

Describe the bug
Cell Range Ctrl-C and Ctr-V produce strange behaviour when column bottomCalc option is added. I tested it with the demo of Range Clipboard on https://tabulator.info/docs/6.2/range section , when there is no bottomCalc option added is OK as the demo shows, but if you add bottomCalc option to the column definition, it will also copy the footer which is the bottomCalc value to the clipboard. And if you ‘paste to fill’ the other cell, it will fill the cell under the cell you want to paste with the bottomCalc value ( for example sum ) which is very strange. What we expect should be the same like what Excel does. Would you please fix that problem? Thank you.

Tabulator Info
Version 6.2.1
Working Example
A little modification of the demo of Range Clipboard on https://tabulator.info/docs/6.2/range section with bottomCalc option added. AS shown in this jsfiddle page:
jsfiddle page
The screen shots:
Ctrl-C

Ctr-V

To Reproduce
1.Range select the second column of the first row(the value is 12).
2. Press Ctrl-C.
3. Select the second column of the second row(the value is 1).
4. Press Ctrl-V.
5. You will see the value of the second column of the second row is 12 which is correct, but the value of the second column of the third row becomes 407(the sum of this column) which is not what we want.

Expected behavior
The cell value under the cell we want to paste or fill to will not be affected.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Ubuntu Linux, Windows 10
• Browser :Firefox , Chromium
• Version: 125.0.2 , 125.0.6422.141
  Additional context
  Add any other context about the problem here.

[guidry]

After taking a look into the Tabulator source code, I finally found that we need to set columnCalcs flag to false in the clipboardCopyConfig option , for example
clipboardCopyConfig:{ rowHeaders:false, columnHeaders:false, columnCalcs:false //*** You have to explicitly add this }
Because columnCalcs flag is not explicitly mentioned in Range Clipboard section of the documentation, I think it would be better to add this to documentation to reduce confusion and prevent this issue from happening.