Show background fetch status in bottom line

[stefanhaller]

• PR Description

This shows a status as if the user had typed 'f' manually in the files panel.

I want this particularly for the first fetch after startup. There are often
situations where I need to wait for this first background fetch to be done
before I can do what I want (e.g. rebase my branch onto its base branch, or
check out a branch that my coworker has told me they just pushed), but currently
it's hard to tell when that is.

For every subsequent background fetch after the first one it is less important,
but it hopefully doesn't hurt, and it might be nice to have some visual
indication that background activity is happening.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 55236801	✅ 0.00%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (5523680)	Report Missing	Report Missing	Report Missing
Head commit (5424785)	52074	45032	86.48%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#4215)	3	0	0.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[jesseduffield]

I quite like the idea of just showing it every time, because often it causes a slight delay in some action I want to perform and it would be good to actually see the reason why.

As for location, I'm fine with it at the bottom. It may be a little bit annoying for users who are hiding their bottom line (because it shows up again and slightly squashes the other panels when something is loading). We've got a separate issue for that here: #4189

[stefanhaller]

Ok cool. Does that mean we can merge this as is (after rewording the commit message a bit)?

Did you see the change in the first commit? I'm not entirely sure about it, see commit message for details.

[jesseduffield]

Yep, I think that's fine. LGTM