Use SPI config ordering for Documentation

[Mordil]

I just added SPI support for hosting DocC documentation, and the output is not following my specified ordering in the YAML file:

builder:
  configs:
    - documentation_targets: ['RediStack', 'RedisTypes', 'RediStackTestUtils']

Instead, it sorts alphabetically, which leaves the module RedisTypes as the entry point for documentation and first in the list of module documentation.

This causes me a problem, because RediStack is the main purpose of the package.

[daveverwer]

Yes, this bug crept in as we transitioned from one mechanism for knowing if a package has documentation to anotheInitiallyally, we used the order in the .spi.yml file for the different archives, but in certain circumstances, the archives produced didn't exactly match the target names. We also needed to know when the build machines finished processing and uploading the documentation archives, so we switched to the doc_archives field, which is populated only when documentation generation completes successfully.

However, you're right that the order should come from the manifest, at least where target names match archive names.

This is a bug, I'll promote it to be an issue now. Thanks Nathan.