Improve upload progress visualization

[susnux]

• Resolves: File-upload: smooth time remaining, bitrate and stabilize user information #30147

Summary

Improving the upload progress bar's "Time remaining". Tested with a single large file and multiple smaller files.
Besides the existing moving average, a smoothing factor is introduced for the time remaining display as well as the bitrate.
Furthermore, half of the buffer needs to be filled before the first prediction is displayed to the user. This reduces volatile and jumping durations towards the user and improves usability.

I extended the origin PR as follows:

• Fixed initial value of smooth* (check for undefined)
• Only show the remaining time if the buffer is fully filled to prevent inconsistent forecasts
• Show number of finished and total uploads, this is required if you upload many files. Otherwise you might not see any progress.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[szaimen]

Tested and seems to work in general, there might be some edge cases though that do not work perfect but that has possibly already been there before. Also didnt review the code

[susnux]

/backport to stable27

[susnux]

/backport to stable26

[susnux]

/backport to stable25

[skjnldsv]

Let's wait for #39808 please

The PR is now merged, lets fix this so we can backport to stable27

[skjnldsv]

Shall this be done for https://github.com/nextcloud-libraries/nextcloud-upload too?

[susnux]

Shall this be done for https://github.com/nextcloud-libraries/nextcloud-upload too?

If it is relevant for the library then yes

[skjnldsv]

If it is relevant for the library then yes

We're using a dedicated library that calculates remaining time and such 🤔 🤷

[susnux]

Cypress seems unrelated

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b fix/foo-stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[backportbot-nextcloud]

The backport to stable26 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable26
git pull origin stable26

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[backportbot-nextcloud]

The backport to stable25 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable25
git pull origin stable25

# Create the new backport branch
git checkout -b fix/foo-stable25

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport