Investigate using time as a factor in the decision about whether to render a large file

[bobsilverberg]

This comes from a discussion with @willdurand, following a discussion that he had with @wagnerand.

We are currently truncating files based on the size of the content of a file, which works, for the most part, to help speed up the UI when navigating between files. It does, however, result in some files being truncated that wouldn't otherwise need to be.

We would like to implement a solution which would allow the app to attempt to render an entire file, and then, after a set period of time has elapsed, would fall back to a different solution. This could be rendering a truncated file, as is being done now, or could be simply displaying a message that the file is too large to render, or perhaps something else we haven't thought of yet. What happens when the attempt to render times out can be decided down the road. For now this issue is about determining how to implement a solution that would attempt to render the file, and would be able to abort that rendering and do something else after a certain period of time elapses.

┆Issue is synchronized with this Jira Task