Introduced improved way to interact with settings in tests

[marcusmoore]

Description

This PR improves the way settings are interacted with in tests. Previously, in most feature tests we would have to set up app settings by adding the following to the top of each test:

Setting::factory()->create()

// or something like
Setting::factory()->withMultipleFullCompanySupport()->create()

Another approach could be to put it in the universal setUp() method but that would nullify our usage of LazilyRefreshDatabase since each test would be refreshing the database regardless of the actual test code needing it.

In addition, subsequent changes to settings had the possibility of not talking practical effect if Setting::getSettings() was called prior to the changes since that method caches settings in a static variable.

This PR introduces a trait and fluent interface for interacting with settings in a similar manner as Laravel's WithFaker trait.

Tests that need to interact with the application's settings should add the InteractsWithSettings trait to the class. Our base TestCase's setUp method checks for this trait and will initialize the app's settings using the Setting factory. It will also allow tests to use the following syntax for updating application settings within tests:

$this->settings->enableMultipleFullCompanySupport();

$this->settings->set(['some' => 'thing']);

Using these methods will clear the settings cache that may have been stored if Setting::getSettings() was called.

Additional helper methods like enableMultipleFullCompanySupport() can be added to the Settings class as they are needed.

Note: I'm avoiding updating the testing docs to document this because I want to use it in other pieces of work a bit to make sure the API is solid.

[what-the-diff]

PR Summary

• Introduced a new trait for test cases
  Added a new trait to make handling settings in tests more efficient.

• Refactored tests using settings
  Updated all relevant tests to use the new trait instead of directly interacting with the database model.

• Simplified settings creation with factory method
  Created a factory method to enable multiple full company support by default, enhancing readability and test setup efficiency.