Add missing privateUrl properties

Overview of the Feature Request

To display a dataset accessing through a privateUrl token we are currently using a js-dataverse use case getPrivateUrlDataset.execute(privateUrlToken) but this use case do not provide all the properties needed to display the full dataset.

These are some properties that we'll have to get from other js-dataverse use cases in order to complete the dataset:

1. Dataset user permissions
2. Dataset locks
3. Dataset files total download size

Note that there are already use cases implemented in js-dataverse to get this dataset data when accessing through dataset id, but we'll need to get them using a privateUrl token to complete the getByPrivateUrlToken() implementation of DatasetJSDataverseRepository

What kind of user is the feature intended for?

All users

What inspired the request?

• https://github.com/IQSS/dataverse-frontend/pull/256#discussion_r1426628454

What existing behavior do you want changed?

None

Any brand new behavior do you want to add to Dataverse?

None

Any open or closed issues related to this feature request?

Start with DatasetJSDataverseRepository.getByPrivateUrlToken() and the existing getPrivateUrlDataset.execute(privateUrlToken) use case. Compare the dataset properties returned through the private URL with the existing use cases for dataset-ID access, including user permissions, locks, and total file download size. Done means the private-token path provides the complete dataset needed for display.