[Enhancement] Enable terminate_on_match for Outcar parser

[DanielYang59]

Re-post from #4034 (comment), need investigation of implications of turning on terminate_on_match of read_pattern for io.vasp.outputs.Outcar parser (at least for those "global" tags that is consistent across the entire run). Sounds like this would speed up initialization by early exit upon hit.

[DanielYang59]

Another related proposal, perhaps we should consider:

• Write a lazy version of read_pattern, to get a collection of all patterns and walk through the file once
  AND/OR
• State machine
• Refactor read_pattern to process in memory