Add rule to check key order

[jeefberkey]

Adds a new rule that for the moment checks that name is the first key on tasks. In the future
we will add additional ordering rules to it.

Partial: #578

[ssbarnea]

@jeefberkey Please update PYTEST_REQPASS and increase its value to match expected number of tests (+2).

[jeefberkey]

Thanks for the additional guidance - rg was ignoring the directory when I was looking for that number.

[ssbarnea]

Thanks for the additional guidance - rg was ignoring the directory when I was looking for that number.

I am an rg user myself, great tool! I have an alias rg='rg --hidden --no-follow --max-columns 255 --no-heading --column -F' that you might like.

[ssbarnea]

@jeefberkey I pushed some minor changes, like removing opt-int, we will make it experimental from start as it is very useful.

[jeefberkey]

Thanks for the test fixes, I was working on them but was sick the past few days. The new test name may conflict with other things I'm working on, but we can deal with that later

[cidrblock]

love it.

[ssbarnea]

Thanks for the test fixes, I was working on them but was sick the past few days. The new test name may conflict with other things I'm working on, but we can deal with that later

Please mention more details about conflicts we might have? While class name is not important, the id of the rule is harder to change once we merge it, so better to get it right from start. I used key-order because I want to evolve this rule to take care of ordering of keys in general.

[jeefberkey]

Nothing, this is actually not a blocker now that I think about it.