Add unit tests for addColumns with various address mapping policies

[sequba]

Context

TBP

How has this been tested?

TBP

Types of changes

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• New feature or improvement (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Additional language file or change to the existing one (translations)
• Change to the documentation

Related issues:

1. addColumns throws an error with AlwaysDense address mapping with empty values #1027

Checklist:

• My code follows the code style of this project.
• I described the modification in the CHANGELOG.md file.
• My change requires a change to the documentation.
• My change requires a migration guide.

[github-actions]

Performance comparison of head (1b9d4b9) vs base (419d776)

                                     testName |  base |  head |   change
------------------------------------------------------------------------
                                      Sheet A | 601.3 | 592.9 |   -1.40%
                                      Sheet B | 252.3 | 255.9 |   +1.43%
                                      Sheet T | 296.8 | 283.3 |   -4.55%
                                Column ranges | 619.8 | 663.1 |   +6.99%
Sheet A:  change value, add/remove row/column |    34 |    38 |  +11.76%
 Sheet B: change value, add/remove row/column |   333 |   367 |  +10.21%
                   Column ranges - add column |   199 |   435 | +118.59%
                Column ranges - without batch |   706 |   624 |  -11.61%
                        Column ranges - batch |   187 |   332 |  +77.54%