Clarify usage of `SAST_BANDIT_EXCLUDED_PATHS`

What does this MR do?

Clarify usage of the SAST_BANDIT_EXCLUDED_PATHS by providing an example.

There is no way for the user to know that the application is mounted under /tmp/app and the scanner doesn't cd into the project directory so relative paths (e.g.: tests/) won't work.

Examples:

• Using SAST_BANDIT_EXCLUDED_PATHS: '*/tests/*' (works): https://gitlab.com/thiagocsf/nexus3-cli/-/jobs/584564359
• Using SAST_BANDIT_EXCLUDED_PATHS: 'tests/*' (does not work): https://gitlab.com/thiagocsf/nexus3-cli/-/jobs/584562936#L152

IMO, a proper fix would be for the SAST scanner to be called from within the root of the application directory.

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• [-] Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team