Improve typing for archived histories API schema

[davelopez]

Part of #18532

Drop "Any" and use a partial model for custom keys. This will improve the client API schema types for archived histories and consolidate the serialization with the regular histories.

Before

responses: {
            /** @description Successful Response */
            200: {
                content: {
                    "application/json": unknown[];
                };
            };

After

responses: {
            /** @description Successful Response */
            200: {
                content: {
                    "application/json": (
                        | components["schemas"]["CustomArchivedHistoryView"]
                        | components["schemas"]["ArchivedHistoryDetailed"]
                        | components["schemas"]["ArchivedHistorySummary"]
                    )[];
                };
            };

How to test the changes?

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[davelopez]

Test failures are unrelated

[bgruening]

Thanks a lot @davelopez for all those typing improvements!