This PR adds a set of expressive helper methods to simplify HTTP status code checks onResponseInterface objects that useCommonResponseTrait trait.

These new methods allow developers to write more readable and intention-revealing code when working withHttpClient.

Before:

// opt-out from exception to manually check$data =$response->toArray(false);if (404 ===$response->getStatusCode()) {// not found}

After:

// opt-out from exception to manually check$data =$response->toArray(false);if ($response->isNotFound()) {// not found}

I've intentionally selected the most common status codes to keep this initial set focused and practical.

That said, I'm open to feedback on:

• the naming of the trait (ResponseStatusCodeTrait)
• whether we should add more methods (e.g., 418 😉) or remove less useful ones
• alternative implementation styles, if more in line with Symfony conventions.

PS: This is my 1st PR to Symfony.