Add Doc: ShouldBeEncrypted Interface to Queue (#8904)

* Add: ShouldBeEncrypted Queue Docummentation

* formatting

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>

queues.md

@@ -7,6 +7,7 @@
     - [Generating Job Classes](#generating-job-classes)
     - [Class Structure](#class-structure)
     - [Unique Jobs](#unique-jobs)
+    - [Encrypted Jobs](#encrypted-jobs)
 - [Job Middleware](#job-middleware)
     - [Rate Limiting](#rate-limiting)
     - [Preventing Job Overlaps](#preventing-job-overlaps)
@@ -338,6 +339,21 @@ Behind the scenes, when a `ShouldBeUnique` job is dispatched, Laravel attempts t
 > **Note**  
 > If you only need to limit the concurrent processing of a job, use the [`WithoutOverlapping`](/docs/{{version}}/queues#preventing-job-overlaps) job middleware instead.
 
+<a name="encrypted-jobs"></a>
+### Encrypted Jobs
+
+Laravel allows you to ensure the privacy and integrity of a job's data via [encryption](/docs/{{version}}/encryption). To get started, simply add the `ShouldBeEncrypted` interface to the job class. Once this interface has been added to the class, Laravel will automatically encrypt your job before pushing it onto a queue:
+
+    <?php
+
+    use Illuminate\Contracts\Queue\ShouldBeEncrypted;
+    use Illuminate\Contracts\Queue\ShouldQueue;
+
+    class UpdateSearchIndex implements ShouldQueue, ShouldBeEncrypted
+    {
+        // ...
+    }
+
 <a name="job-middleware"></a>
 ## Job Middleware