Email notification sent when new dataset version is published confuses users about the state of their dataset

[jggautier]

Overview of the Feature Request
A depositor of a dataset in the Harvard Dataverse Repository was confused by the email notification that the Dataverse software sends (in at least version 4+ of the software) when a new version of their dataset was published. This was because the email was the same email sent when the first version of the dataset was published. The email led the user to wonder if the dataset had ever been published.

How can the email notifications sent when dataset versions are published more clearly describe what's happened to their dataset?

Would the state of datasets be more clear to users if, when a new version of a dataset is published, the email notification sent specifies that a new version of the dataset has been published?

What kind of user is the feature intended for?
API User, Curator and Depositor

What inspired the request?
A conversation with a dataset depositor who was confused by the email notification sent when someone published a new version of their dataset. This was also noticed earlier when reviewing the notifications that the Dataverse software sends.

What existing behavior do you want changed?
The email notification that is sent when someone publishes a dataset version of a published dataset.

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

Any related open or closed issues to this feature request?

[TaniaSchlatter]

This also applies to the email sent when a draft dataset is created. The email does not specify that a DRAFT was created, and that the dataset needs to be published. v.5.10