Determine error view and message based on type

...not based on status code.

To simplify this logic, we now use the same error "type" both when
routes are not found and specific models are not found. One exception is
ours, one is from Laravel, but for the purposes of error handling they
should be treated the same.

Fixes flarum/core#1641.

views/error/csrf_token_mismatch.blade.php

@@ -6,7 +6,7 @@
   </p>
   <p>
     <a href="javascript:history.back()">
-      {{ $translator->trans('core.views.error.419_return_link') }}
+      {{ $translator->trans('core.views.error.csrf_token_mismatch_return_link') }}
     </a>
   </p>
 @endsection

views/error/not_found.blade.php

@@ -6,7 +6,7 @@
   </p>
   <p>
     <a href="{{ $app->url() }}">
-      {{ $translator->trans('core.views.error.404_return_link', ['{forum}' => $settings->get('forum_title')]) }}
+      {{ $translator->trans('core.views.error.not_found_return_link', ['{forum}' => $settings->get('forum_title')]) }}
     </a>
   </p>
 @endsection