EDPUB-1729: Update File Upload Module Component

[acharya-deepak]

Description

Disable upload button and grey out after being clicked
Update file upload component to include a time estimate for users
Update file upload component to include file checksum calculation in progress bar to avoid sudden jumps in progress after long period of loading
Don't query createTempUploadFile if file fails to upload
Add help icon to File Status header to provide additional information about available statuses and what this means for the file's availability
Add error handling display, so a user can be presented the error encountered during upload in the case of a failed upload
Remove wording restricting uploads to < 5GB

Linked JIRA Task or Github Issue

JIRA Task: [example](https://bugs.earthdata.nasa.gov/browse/EDPUB-1729)

Github Issue: example

Types of changes

What types of changes does your code introduce to Earthdata Pub (EDPub)?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if adding or updating the existing documentation resources)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the Contributing Guide
• I have updated the CHANGELOG
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Validation Steps

This will help us get a jump start on validating your PR by describing the steps to replicate
and validate the expected behavior. (For an example of good validation instructions, check out Bryan's Bouncy Ball PR.)

1. Make sure all merge request checks have passed (CI/CD).
2. Pull related branches locally.
3. Navigate to fileupload section and attempt to upload new files, ensuring they meet the acceptance criteria