Remove legacy history usage from js-modules

[guerler]

Follow-up #14630. Decouples remaining js-modules from legacy history as another step towards its removal. The following is a list of modules which need to be decoupled. This PR also contains fixes and simplifications for the history store. With these changes details of a history are not deleted if in a consecutive request only obtains partial data (summary serialization) from the backend. Additionally this PR resolves the code duplication of collection builders from the library dataset js-modules.

• Data library
• History view
• History grid

There are two remaining makos which use the legacy history. These are the history's display and embedded makos which will be refactored in a follow-up. Initially this PR attempted to include these changes but it makes more sense to separate the two.

How to test the changes?

(Select all options that apply)

• 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.

[bgruening]

I tested the history and the libraries and it seems to work well.

Thanks @guerler

[mvdbeek]

Thanks @guerler!