Add folder decisions to settings export

* feat:SP-1929 Includes src folder on settings export

* chore:SP-1943 Add unit tests for settings export

* chore:SP-1944 Adds integration tests

* chore:SP-1951 Adds glob patterns to settings export

* feat:SP-1987 Ingest SCANOSS settings

* chore:SP-1997 Adds SCANOSS Settings documentation

* Upgrades app version to v1.15.5

* chore:SP-2005 Hides API Key on ProjectSettings screen

* bug:SP-2006 Fixes bug on venv indexing

* Upgrades scanoss version to v0.15.5

Author: agustingroh

README.md

@@ -119,6 +119,115 @@ Example structure of the file:
   }
 ]
 ```
+# SCANOSS Settings File
+SCANOSS provides a settings file to customize the scanning process. The settings file is a JSON file that contains project information and BOM (Bill of Materials) rules. It allows you to include, remove, or replace components in the BOM before and after scanning.
+
+### Settings
+The ``scanoss.json`` object allows you to configure various aspects of the scanning process. Currently, it provides control over which files should be skipped during scanning through the ``skip`` property.
+
+
+### BOM Rules
+
+The ``bom`` section defines rules for modifying the BOM before and after scanning. It contains three main operations:
+
+### 1. Include Rules
+
+Rules for adding context when scanning. These rules will be sent to the SCANOSS API meaning they have more chance of being considered part of the resulting scan.
+
+
+
+    {
+        "bom": {
+            "include": [
+                {
+                    "path": "/path/to/file",
+                    "purl": "pkg:npm/[email protected]",
+                    "comment": "Optional comment"
+                }
+            ]
+        }
+    }
+
+### 2. Remove Rules
+
+Rules for removing files from results after scanning. These rules will be applied to the results file after scanning. The post processing happens on the client side.
+
+
+    {
+        "bom": {
+            "remove": [
+                {
+                    "path": "/path/to/file",
+                    "purl": "pkg:npm/[email protected]",
+                    "comment": "Optional comment"
+                }
+            ]
+        }
+    }
+
+### 3. Replace Rules
+
+Rules for replacing components after scanning. These rules will be applied to the results file after scanning. The post processing happens on the client side.
+
+    {
+        "bom": {
+            "replace": [
+                {
+                    "path": "/path/to/file",
+                    "purl": "pkg:npm/[email protected]",
+                    "replace_with": "pkg:npm/[email protected]",
+                    "license": "MIT",
+                    "comment": "Optional comment"
+                }
+            ]
+        }
+    }
+
+
+# Matching Rules
+
+
+1. **Full Match**: Requires both PATH and PURL to match. It means the rule will be applied ONLY to the specific file with the matching PURL and PATH.
+2. **Partial Match**: Matches based on either:
+   - PURL only (PATH is optional). It means the rule will be applied to all files with the matching PURL.
+ 
+Example Configuration
+---------------------
+
+Here's a complete example showing all sections:
+
+
+    {
+        "bom": {
+            "include": [
+                {
+                    "path": "src/lib/component.js",
+                    "purl": "pkg:npm/[email protected]",
+                    "comment": "Include lodash dependency"
+                }
+            ],
+            "remove": [
+                {
+                    "purl": "pkg:npm/[email protected]",
+                    "comment": "Remove deprecated package" 
+                }
+            ],
+            "replace": [
+                {
+                    "path": "src/utils/helper.js",
+                    "purl": "pkg:npm/[email protected]",
+                    "replace_with": "pkg:npm/[email protected]",
+                    "license": "MIT",
+                    "comment": "Upgrade to newer version"
+                }
+            ]
+        }
+    }
+
+Usage
+-----
+
+You can add your 'scanoss.json' on the root of your project
 
 
 ## [Collaborative Workspace](COLLAB_WORKSPACE.md)

package-lock.json

@@ -152,7 +152,7 @@
     "react-virtualized-tree": "^3.4.1",
     "reflect-metadata": "^0.1.13",
     "regenerator-runtime": "^0.13.5",
-    "scanoss": "^0.15.2",
+    "scanoss": "^0.15.5",
     "sort-paths": "^1.1.1",
     "source-map-support": "^0.5.19",
     "translation-check": "^1.0.2",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "scanoss-workbench",
-  "version": "1.15.4",
+  "version": "1.15.5",
   "description": "Desktop version to use SCANOSS OSS in your projects",
   "license": "GPL-2.0-only",
   "author": {