minor #18331 Improve error_pages.rst (edent)

This PR was submitted for the 6.2 branch but it was merged into the 5.4 branch instead.

Discussion
----------

Improve error_pages.rst

I couldn't find any explicit documentation about `{{ exception.message }}`

This adds it in and provides a link to to class so that readers can find the other methods available.

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `6.x` for features of unreleased versions).

-->

Commits
-------

0cc61f7 Update error_pages.rst

Author: javiereguiluz

controller/error_pages.rst

@@ -114,10 +114,14 @@ store the HTTP status code and message respectively.
     and its required ``getStatusCode()`` method. Otherwise, the ``status_code``
     will default to ``500``.
 
-Additionally you have access to the Exception with ``exception``, which for example
-allows you to output the stack trace using ``{{ exception.traceAsString }}`` or
-access any other method on the object. You should be careful with this though,
-as this is very likely to expose sensitive data.
+Additionally you have access to the Exception with ``exception``.
+This allows you to access any method of :class:`Symfony\\Component\\HttpKernel\\Exception\\HttpException`.
+For example, if an exception message has been set, using 
+``throw $this->createNotFoundException('The product does not exist');``,
+this can be accessed with ``{{ exception.message }}``.
+You can output the stack trace using ``{{ exception.traceAsString }}`` 
+You should be careful with this though, as it is very likely to expose 
+sensitive data.
 
 .. tip::