Fix interference of entity prefetching data with store state

[kschiffer]

Summary

This quickfix fixes an issue with the entity fetching store logic in the Console redesign branch, related to how entities are prefetched for the top entities logic.

Changes

• Introduce new actions for fetching entities without affecting the pagination store which stores the IDs of a particular pagination request
• Update the create-request-logic middleware to allow for logics with multiple action types.

Testing

Steps

1. Go to the application list view
2. (As admin) click on the "All" tab
3. Refresh
4. See the correct tab being active and the correct entities being still shown

Notes for Reviewers

Some more background:
Previously I was using the regular GET_XXX_LIST-actions, which connect to the pagination reducer (pkg/webui/lib/store/reducers/pagination.js). This means that they store the list of IDs that are connected to the paginated requests, so that the Console can select them from the global list of entities and show them in the current list view. Currently the list actions run concurrently and whichever resolves last will win (I've also removed latest option for this reason), which can sometimes be the prefetch for the top entities. If we just fetch the entities to have them in the store, we don't want to mess with the pagination store, as they are not meant to be displayed the current list view. Hence, creating a new set of FETCH_XXX_LIST-actions which do the same as the regular GET_XXX_LIST except storing the IDs in the pagination store will resolve this issue.

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Testing: The steps/process to test this feature are clearly explained including testing for regressions.
• Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.