refactor(Dataset): change endpoints from V3 to V4

[abdimo101]

Description

Short description of the pull request

Motivation

Background on use case, changes needed

Fixes:

Please provide a list of the fixes implemented in this PR

• Items added

Changes:

Please provide a list of the changes implemented by this PR

• changes made

Tests included

• Included for each change/fix?
• Passing? (Merge will not be approved unless this is checked)

Documentation

• swagger documentation updated [required]
• official documentation updated [nice-to-have]

official documentation info

If you have updated the official documentation, please provide PR # and URL of the pages where the updates are included

Backend version

• Does it require a specific version of the backend
• which version of the backend is required:

Summary by Sourcery

Migrate dataset-related frontend logic to support both legacy and V4 dataset representations while using V4 APIs for dataset retrieval and related data.

New Features:

• Introduce a unified CurrentDataset type that can represent both V3 and V4 dataset payloads with optional attachments, datablocks, origdatablocks, and history.

Enhancements:

• Update NgRx dataset state, actions, and effects to store and work with the new CurrentDataset type instead of the obsolete V3-only DTO.
• Adjust components and services that consume datasets (details, batch view, reduce flow, lifecycle, logbooks, admin, uploader, archiving) to operate on CurrentDataset and related V4 DTOs.
• Simplify related datasets queries by delegating sorting to the backend rather than passing a client-side sort field.