Vulnerability scan shows failure when started by Read Only user
**Describe the bug**
When a read only user starts a vulnerability scan on the console, it shows `Failed` status on the side panel.

**To Reproduce**
Steps to reproduce the behavior:
1. Login as a read only user.
2. Go to topology tab and select an Agent to show the side panel.
3. Click on 'Vulnerability Scan' on the side panel
4. Click on 'Start Scan' to start a vulnerability scan
5. Scan fails to start, but the side panel starts showing `Failed` status for 'Vulnerability Scan'

**Expected behavior**
'Vulnerability Scan' status should remain as it is before the scan is started by a read only user, since a read only user is not authorized to start a vulnerability scan.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Components/Services affected**

- [ ] UI/Frontend
- [x] API/Backend
- [ ] Agent
- [ ] Deployment/YAMLs
- [ ] CI/CD Integration
- [ ] Other (specify)

**Additional context**
An additional row is created in the Vulnerability Scans table. This should also not persist since the read only user is not authorized to perform the scan.

diff --git a/deepfence_backend/api/vulnerability_api.py b/deepfence_backend/api/vulnerability_api.py
index 180b3e4e9..34c95c28f 100644
--- a/deepfence_backend/api/vulnerability_api.py
+++ b/deepfence_backend/api/vulnerability_api.py
@@ -1069,6 +1069,7 @@ def vulnerability_csv_download():
 
 @vulnerability_api.route("/add-cve-scan-log", methods=["POST"])
 @jwt_required
+@non_read_only_user
 def cve_scan():
     """
     Add a CVE scan document to Elastic search
['deepfence_backend/api/vulnerability_api.py']