Fragile tests relying on exact messaging of lintr output

What happened?

These two tests break under the current development version of R which is in the process of being released to CRAN:

https://github.com/pharmaverse/logrx/blob/f6c24f87829d1d78d63801ab942baf367eb27625/tests/testthat/test-get.R#L181-L189
https://github.com/pharmaverse/logrx/blob/f6c24f87829d1d78d63801ab942baf367eb27625/tests/testthat/test-writer.R#L199-L209

In general, I try and avoid relying on fragile things like "the exact wording of an error message produced by an upstream package".

For example, in {data.table}, we have this list of messages/message factories for test outputs that come directly from {base} R:

https://github.com/Rdatatable/data.table/blob/c29e313dac1de8b959f5e3438c33c0d00873be05/inst/tests/tests.Rraw#L176-L201

I will submit a quick-fix PR shortly, but it's worth thinking through a more robust way to structure these tests going forward.

Session Information

No response

Reproducible Example

No response

Start with tests/testthat/test-get.R lines 181-189 and tests/testthat/test-writer.R lines 199-209, then inspect how the tests assert lintr output and compare the upstream-message examples linked in the issue. The work is done when both tests remain valid across the current R release without depending on exact upstream error wording.