`vaultenv` secrets file parsing issues

[Riscky]

If one creates a secrets file like this:

VERSION 2

mount secret
example#secret

and run vaultenv with this secret file, it will not load any of the secrets defined beyond the mount statement.
This is unexpected behavior, I would expect a parse error (preferably with a suggestion on how to fix the file).
If VERSION is written with lowercase letters, we do get a parse error:

[ERROR] example.secrets:1:8:
  |
1 | version 2
  |        ^
unexpected space
expecting '#' or path component

If any other lowercase string is put on a single line (without # or /), we get the same behavior: any secrets below it are secretly ignored.

[Riscky]

We discovered another problem with the parser: vaultenv is supposed to ignore comments, but it just silently ignores the rest of the file when it encounters a comment

[maartenberg]

Another fun case: if your secrets file does not end in a newline, the last secret in the file is silently ignored.