api: apply consistent behaviour of the reverse query parameter

[lgfa29]

The reverse query parameter uses GetReverse to traverse the go-memdb table in the opposite order. Initially (#12186) this was used to return results in ascending or descending chronological order, but since this was only possible in some situations where the table schema allowed the reverse query parameter would only work in some specific combination of query parameters.

Given that there is no inherit meaning in using Get or GetReverse (they are just opposite orders to traverse results) the reverse query parameter can actually be used in most situations.

This PR adds the sort argument to state store functions used by the list endpoints that have been updated so far. If sort is SortReverse, the GetReverse method is used and results are returned in the reverse order from the default.

No changelog required since it's continuation of #12186.

[shoenig]

LGTM!

[shoenig]

I assume that CSI test is unrelated, but might want to rebase on main just in case

[hashicorp-cla]

All committers have signed the CLA.

[lgfa29]

I assume that CSI test is unrelated, but might want to rebase on main just in case

Ah yeah, it was fixed here: #12245

Rebased just in case to double-check.

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.