Fixed #10224: fix route names for optimize command

[dbakan]

Description

Fixes some duplicate route names in routes/api.php for the Api\AssetFilesController:

• api.assets.files was used for both list and store
• api.assets.file was used for both show and destroy

This led to artisan route:cache and artisan optimize to fail (also see #11595 which fixed this for web routes).

This PR also introduces a new OptimizeTest to ensure that artisan optimize runs successfully.

Fixes #10224

Type of change

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

How Has This Been Tested?

• Tests\Feature\Console\OptimizeTest

[welcome]

💖 Thanks for this pull request! 💖

We use semantic commit messages to streamline the release process and easily generate changelogs between versions. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix if it doesn't have one already.

Examples of commit messages with semantic prefixes:

• Fixed #<issue number>: don't overwrite prevent_default if default wasn't prevented
• Added #<issue number>: add checkout functionality to assets
• Improved Asset Checkout: use new notification method for checkout

Things that will help get your PR across the finish line:

• Document any user-facing changes you've made.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[what-the-diff]

PR Summary

• Implementation of a New API Route
  A fresh API path has been incorporated to enhance our system's accessibility and functionality. This new route, named ‘/api/assets/files’, is now available and its name has been updated in the routes/api.php file.

• Updated API Endpoints in Testing
  Adjustments have been done to the API endpoints in our test files, more precisely, in tests/Feature/Assets/Api/AssetFilesTest.php. They now utilize the newly named route, which harmonizes our testing with the latest changes and assures the continuation of robust, efficient testing of our API routes.

• Addition of a New Test Case
  The advent of a new file, tests/Feature/Console/OptimizeTest.php, introduces a test case for the optimize command to the system. This is a step towards increased system resilience by ensuring this command operates correctly and meets our operational and performance standards.

[snipe]

Thanks! This PR seems fine - we don't use the route:optimize console command, but it shouldn't hurt anything. Can you please re-target to the develop branch though, per the developer docs?

[dbakan]

Thanks! I changed the target branch to develop. Sorry I missed that.

[snipe]

Thanks! Looks like you might need to rebase. There's a bunch of stuff in there outside of this PR's changes files/commits.

[dbakan]

Yeah, you're right. I hope it's fixed now.

[welcome]

Congrats on merging your first pull request! 🎉🎉🎉