Add MobSF in SAST vendor template

What does this MR do?

These changes are related to this issue: #259830 (closed)

The purpose of this MR is to add MobSF in SAST vendor template. As this feature is not fully tested, this is hidden behind SAST_EXPERIMENTAL_FEATURES.

Tests

The following are tests that prove whether SAST_EXPERIMENTAL_FEATURES is working for different mobile projects.

• Android project: gitlab-org/security-products/tests/java-android!1 (closed)
• ios: gitlab-org/security-products/tests/objective-c!1 (closed)

Here is a test if SAST_EXPERIMENTAL_FEATURES is disabled: gitlab-org/security-products/tests/java-android!2 (closed)

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