`dataverse_json` export contains `storageIdentifier`, which exposes internal configuration properties

• What steps does it take to reproduce the issue?

Export a dataset as datavers_json. For example: https://dataverse.harvard.edu/api/datasets/export?exporter=dataverse_json&persistentId=doi%3A10.7910/DVN/EJLMJH

• When does this issue occur?
  When I export a dataset as datavers_json. For example: https://dataverse.harvard.edu/api/datasets/export?exporter=dataverse_json&persistentId=doi%3A10.7910/DVN/EJLMJH

• Which page(s) does it occurs on?
  On every dataset page when I export as datavers_json and also within the export API.

• What happens?
  The export contains the properties storageIdentifier, which is not really useful fo end users and exposes internal storage configuration to the public. For example:

storageIdentifier: "s3://10.7910/DVN/EJLMJH"
datasetVersion : {
storageIdentifier : "s3://10.7910/DVN/EJLMJH"
}
files :[  
{  
dataFile {  
storageIdentifier : "s3://dvn-cloud:193d764e846-2fc4cee84513"
}}]

• To whom does it occur (all users, curators, superusers)?
  all users

• What did you expect to happen?
  That the storageIdentifier is not part of the dataverse_json-export

Which version of Dataverse are you using?
6.5

Any related open or closed issues to this bug report?
I found none.

Are you thinking about creating a pull request for this issue?
Yes.

Start by reproducing the export through the datasets/export API with exporter=dataverse_json and the example persistent ID. Trace the dataverse_json exporter and its existing tests to identify where storageIdentifier is included. Done means the export API and dataset-page export omit storageIdentifier while retaining the other expected metadata.