5886 link harvested datasets via api

[sekmiller]

What this PR does / why we need it:
Allows a user to link a harvested dataset via the api. Previously there was a test that required that the dataset be published before it could be linked. This expands the test to allow datasets that haven't been published but are harvested to be linked

Which issue(s) this PR closes:

Closes #5886

Special notes for your reviewer:
I wasn't able to come up with a way to test this in the integration test. Any suggestions here would be welcome. (I tested by manually giving an unpublished dataset a dummy harvesting client id)

Suggestions on how to test this:

Does this PR introduce a user interface change?:
no

Is there a release notes update needed for this change?:
no

Additional documentation:
None

[coveralls]

Coverage remained the same at 19.632% when pulling 988572b on 5886-link-harvested-datasets-via-api into 91ddb11 on develop.

[kcondon]

@sekmiller I have some questions when you have a minute:

1. how does it fix the issue it closes since it appears to be ui related and create dataset related.
2. how can you harvest unpublished datasets for them to be linked in the first place?

[scolapasta]

Right, the issue wasn't unpublished, harvested (which can't exist), but (some) harvested datasets being identified as unpublished, possibly because they were missing a publication date in the db.

[kcondon]

@scolapasta Do you have a known test case? Also, what about the issue it purports to close with the JSF errors?

[scolapasta]

JSF issue was just a type - 5586 instead of 5886. (I just fixed it for @sekmiller in the description)

[scolapasta]

as for test cases, here is a search results of four harvested datasets in production that could not be linked:

https://dataverse.harvard.edu/dataverse/harvard?q=covid+coronavirus&fq1=metadataSource%3A%22Harvested%22&fq0=dvObjectType%3A%28dataverses+OR+datasets+OR+files%29&types=dataverses%3Adatasets%3Afiles&sort=score&order=

(can't link to dataset pages of course, because they don't have any. - here are there dbids for the API: 3822842, 3724321, 3767398, 3767393 )

[kcondon]

@scolapasta Thanks, just found that out from Julian as well.

[kcondon]

@sekmiller This works now except for the case where the dataset is unpublished, it shows an incomplete error: {"status":"ERROR"} rather than {"status":"ERROR","message":"Can't link a dataset that has not been published"}

Update: this was due to languages being enabled and the lang bundle not yet having the new key. When we use the default bundle, it works as expected.