Pipelines in 'Create Project' page are confusing

Several of the ScanCode.io v35.3.0 built-in pipelines are confusing - to me and others they look to be doing roughly the same thing.

Talking about pipelines in below table - for a user new to ScanCode.io the words "analyze", "inspect", "resolve" and "scan" all basically mean the same. The static and dynamic resolving of dependencies seems "bolted on" to me.

Believe we should simplify the current built-in pipelines for a better user experience so the user is more likely to instantly pick the pipeline that's applicable to their use case. Ideally the UI would be 'smart' - meaning based on given inputs try to automatically select the pipeline that is most relevant

| Pipeline | Description |
|---|---|
| inspect_packages | Inspect a codebase for packages and pre-resolved dependencies.|
| resolve_dependencies| Resolve dependencies from package manifests and lockfiles.|
| scan_codebase | Scan a codebase for application packages, licenses, and copyrights.|
| scan_single_package | Scan a single package archive (or package manifest file).|