Add text and messaging to help users know size limits and file status when ingest is not attempted due to file size being over the limit

[TaniaSchlatter]

This issue was originally opened for Harvard Dataverse #132, but can be addressed for all installations.

There is no message when files fail ingest due to being over the size limit.

This issue is for adding informational text and feedback messaging to the UI to help users know:

• file size limits for tabular data may be different than general file size limits, and
• when a tabular file that exceeded the ingest limit is available but was not ingested, and has limited tabular file features.

This enhancement will be useful for depositors and anyone uploading to help know the status when a data file is not ingested due to size.

[TaniaSchlatter]

Proposed solution:

1. Help users know the limit for tabular file ingest by adding text that specifies the limit for tabular ingest in the upload widget. This text is already dynamic, based on limits defined for the dataset collection the file is added to. Example for Harvard Dataverse default collection:

Provide the link to relevant page in the guides, ex: https://guides.dataverse.org/en/latest/user/tabulardataingest/index.html

2. Show a message on the file table that provides the status of the file to the depositor:
   

[djbrooke]

• Item 1. is uncontroversial. The message will be longer if there are type-specific limits (such as the lower limit for R files in Havard Dataverse Repository).
• For 2., only the dataset owner would see the message, and it would not need to persist. We could also instead provide the message right after upload, similar to how we provide the "ingest in progress" messages when ingest is starting.

[pdurbin]

For 2., only the dataset owner would see the message, and it would not need to persist. We could also instead provide the message right after upload, similar to how we provide the "ingest in progress" messages when ingest is starting.

@djbrooke As discussed during sprint planning, we don't actually store this "file exceeds the limit for ingest" anywhere so I didn't implement anything for this in pull request #8271. If we still need something here, let's talk about it.