Cache Invalidation for SSH Edits

[rosenbrockc]

When files are edited over tramp they get cached until the file is modified. The routine that invalidates the cache only runs whenever a module is requested to be loaded either directly or as a dependency of another module. Lots of developers save their file every minute out of habit; if the file on the remote server changes often, we don't necessarily want to keep reparsing it over SSH because it takes time and could impede the responsiveness of the auto-completion suggestions.

Perhaps it is good to enable a longer cache duration for SSH edits (e.g. 10 minutes) during which time the file won't be reparsed even if there is a newer version on disk. The fortpy:reparse-buffer-file function could still force the reparse manually, but it wouldn't be automated. Since we do have real-time update of code, I don't think it would adversely affect the developer experience much.

[rosenbrockc]

Added a one minute delay between checks of the file modification time for both SSH and non-SSH isense. After a minute has elapsed, the file is reparsed using the regular logic that makes sure it has actually been modified before reading it again from disk or cache.