Undo optimize command in test after it is completed

[marcusmoore]

Description

This PR follows up on the test introduced in #15082 by cleaning up the cached config and routes that are generated when running the artisan optimize command after the test is run since it can cause some unexpected behavior on local environments.

Type of change

• Bug fix (non-breaking change which fixes an issue)

[what-the-diff]

PR Summary

• Enhanced Test File
  The file OptimizeTest.php in the tests/Feature/Console section has been updated. The changes will improve the way we test our console functionalities.

• Added New Event
  A new event named beforeApplicationDestroyed was introduced. This event triggers two commands — config:clear and route:clear, right before shutting down the application. This action ensures that our system is clean and ready for a new start next time.

• Updated Test Method
  The method testOptimizeSucceeds has now been updated to include the new event. This demonstrates that despite the inclusion of new events, our optimization command is still effectively working as expected.