Remove priority key and change delete tag execution logic

[vakssonya]

We are encountering an issue where columns are not being removed correctly using the Delete tag. This occurs because the deletion order depended on the PriorityKey calculation. The higher the PriorityKey, the sooner the column will be deleted. The current PriorityKey calculation algorithm depends on the number of priorities defined for each tag.

var map = Enumerable.Range(byte.MinValue, byte.MaxValue + 1).ToList();
map.RemoveAll(x => this.Any(t => t.PriorityKey == x));
tag.PriorityKey = (byte)map.OrderBy(x => Math.Abs(tag.Priority - x)).First();

For the Delete tag, the Priority is 5, and in the case of PriorityKey calculation for 10 Delete tags in one row sequentially
the PriorityKey value will be - 5 4 6 3 7 2 8 1 9 0. This is incorrect behavior, and this MR presents a solution that sorts tags based on the main priority of the tag. For all tags except delete, the execution order of tags with the same priority is assumed from 1 cell to the last, when for delete tags the execution order from the last cell to the first is assumed.

[Pankraty]

In general, I would recommend not to put "arrange" and "act" in one method - it is harder to grasp the idea of tests this way.

Extract tagList.Execute... into a separate method (e.g. Act(IXLRange range)) and rename the setup methods to womething like AddTagsToRange, AddTagsToWorksheet. Besides, by making cells the last parameters, you can utilize params keyword and make the invocation yet simpler:

AddTagsToRange(rng, "B2");
AddTagsToWorksheet("A3", "A4", "C1", "D1");

[Pankraty]

Can we prepare another template, maybe with simpler structure but with all different options for placing <<delete>> tag - in the first column, in the first row, and a few in a table range?

Something like this

In the expected result, there should be no red cells, easy to visually check.

[Pankraty]

Also, it would be amalizing if you can cover conditional delete with a test.

[vakssonya]

This solution will not fix deleting rows after or inside named range, it requires additional recalculation of the tag cell address. We will try to provide a solution for these cases, but for now the column deletion needs to be fixed

[Pankraty]

Awesome job! Thanks for the contribution and keep going ;)