->toBeAnonymous() expectation in Arch

[aon4o]

Recently I had a problem while writing a test for a modular Laravel 10 app.
The behavior of the DatabaseTransactions trait was really strange.
The tests that used it were failing because the trait tried to execute some migrations which isn't something that's supposed to happen.
After that, I found that the problematic migrations were the only ones in the project that weren't anonymous classes.
After I changed them to be anonymous, everything started working like it should have.

I found some articles about why Laravel switched to anonymous migration classes:

• https://laravel-news.com/laravel-anonymous-migrations
• https://medium.com/@prevailexcellent/why-you-need-to-use-anonymous-migrations-in-laravel-8-9-2be0e0baf0a0

In my opinion, a new expectation ->toBeAnonymous() would have prevented that problem in my project and would be a great addition to the Arch plugin.