[4.x] Implement find or fail on EntryRepository

[benfurfie]

Key deets

Targets: [4.x]
Closesstatamic/ideas#1126

What?

This PR introduces a new method to the EntryRepository - findOrFail. This method can be used to throw an error when an entry is not found, so that error monitoring tools such as Sentry, Flare, Rollbar etc can pick up on it and proactively alert developers.

It also brings Statamic more into line with Laravel's conventions, making it easier for developers to onboard, and to integrate existing Laravel packages that require findOrFail methods.

How

Assuming an entry exists, (say 'home' as this exists with all new Statamic installs)

useStatamic\Facades\Entry;
...$id = 'home';
Entry::findOrFail($id);

This will behave the same way as the find method does currently.

However, let's say we attempt to call an entry that does not exist:

useStatamic\Facades\Entry;
...$id = 'not-home';
Entry::findOrFail($id);

This will throw the new EntryNotFoundException. This exception handles the error and returns the id that was not found. This exception enables it to be picked up by error trackers, and also returns useful information to the developer (i.e. the id not found to the developer assuming they have debug mode enabled).

Testing

I have written tests for the following cases:

• Expect an exception to be thrown when a developer attempts to call an entry that does not exist when the id is a string.
• Expect an exception to be thrown when a developer attempts to call an entry that does not exist when the id is a int.
• That the entry is returned and no errors are thrown when an entry exists and the id is a string.
• That the entry is returned and no errors are thrown when an entry exists and the id is an int.

Anything else?

This PR also adds typehinting and return types to the method to assist with updating Statamic to run with Laravel 11 and PHP8.3.

[duncanmcclean]

This looks great - thanks!

I've made a few tweaks to the exception message and simplified one of the tests. I've also rebased this PR on master since adding a method to the EntryRepository is a breaking change for those implementing their own repositories.

[jasonvarga]

This is so small it might as well be in 4.x. I've just avoided adding it to the interface. We can do that for v5.