Allow endless recording

[henrygerardmoore]

Resolves #31 and doesn't require users to change their usage really at all, just adds 0 as a sentinel value.

Also takes care of this issue I saw in pre-commit:

[WARNING] repo `https://github.com/pre-commit/pre-commit-hooks` uses deprecated stage names (commit, push) which will be removed in a future version.  Hint: often `pre-commit autoupdate --repo https://github.com/pre-commit/pre-commit-hooks` will fix this.  if it does not -- consider reporting an issue to that repo.

My question regarding this change is: should we have the default reset time be 0? As mentioned in #31, I can understand wanting a different default behavior. I also understand not wanting to fill the disk super quickly though, especially since there's no way to ensure a user sees a warning in the docstring. I am open to other suggestions on this, but thought I'd make this PR just to start discussion.

Some other possibilities I considered:

• Still reset the recording, but with incrementing filenames (as mentioned in Automatically RestartRecording - Questionable default behavior #31). Though this is easy to do, I opted to make the PR as-is since it is the smallest code change.
• Change the default to 'swap' between two recordings, so you have at most 2x reset_time of data used. This way, when you reset, you don't just delete all the data. You always have at least the last reset_time data saved. Perhaps a more forgiving default behavior, but maybe a little odd