CHIA-1943 Order header blocks by height in get_header_blocks_in_range

[AmineKhaldi]

Purpose:

This allows us to provide a start and (inclusive) end height and get header blocks in that order.

Current Behavior:

The order depends on whether we'll find blocks in the cache or fetch them from the DB.

New Behavior:

We'll maintain the order of the input heights despite fetching blocks from both cache and DB.

[arvidn]

why is this an improvement?
If there is a good reason to do this, we would need a test as well

[AmineKhaldi]

why is this an improvement? If there is a good reason to do this, we would need a test as well

My understanding is that FullNodeAPI's request_block_headers returns block headers in the order of the input range, so this is done to maintain that behavior so I can leverage get_header_blocks_in_range in my plan to simplify that endpoint.

I've added a test that fails in main and passes with the PR.