Update code owners for smt2

[peterschrammel]

@allredj and @romainbrenguier do some work on the SMT2 front/backend to enable string solver benchmarking. It would be good to get them to review PRs in this part of the code base.

• Each commit message has a non-empty body, explaining why the change was made.
• Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
• The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
• Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
• My commit message includes data points confirming performance improvements (if claimed).
• My PR is restricted to a single feature or bugfix.
• White-space or formatting changes outside the feature-related changed lines are in commits of their own.

[allredj]

✔️
Passed Diffblue compatibility checks (cbmc commit: 23c245e).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/94268288