BUG - Remove CF flow from the ADP Generator and fix template resolution problem

[nikmace]

Related Feature

Feature request: 3514

Description

The CF code for the CF flow of the ADP Generator should be disabled for the time being. The functionality will be turned off by default and can only be accessed by turning on internal enablement and installing the old ADP extension.
Another problem is when using the bundled generator and going through the CF flow, we get the following error during generation:

[2025-10-15 07:54:24] INFO: Creating service instance 'cf_mta_project_1760514864943-xsuaa' of service 'xsuaa' with 'application' plan
[2025-10-15 07:54:24] ERROR: Failed to parse xs-security.json file: Error: ENOENT: no such file or directory, open '/extbin/globals/pnpm/5/.pnpm/@sap+generator-fiori@1.19.2-pre-20251014204951-f4ae19b04.0/node_modules/@sap/templates/cf/xs-security.json'
[2025-10-15 07:54:24] ERROR: {}
[2025-10-15 07:54:24] ERROR: Writing phase failed: Error: Failed to create the service instance: 'cf_mta_project_1760514864943-xsuaa'. Error: The xs-security.json file could not be parsed. Ensure the xs-security.json file exists and try again.
          An error occured while running @sap/fiori:adp#writing

Steps to Reproduce

Steps to reproduce the behavior:

1. Go to staging
2. Select CF ADP extension and the newest master build, and create the dev space
3. Login into CF and open ADP Generator
4. Select CF environment and go through the generator
5. Click finish and see error in the logs

Expected results

CF flow is disabled and not visible to the users
CF generation does not produce errors during writing phase

Actual results

CF flow is visible in case the old adp extension is installed
CF generation errors out

Screenshots

If applicable, add screenshots to help explain the problem.

Version/Components/Environment

Add any other context about the problem here
OS:

• Mac OS
• Windows
• Other

Root Cause Analysis

Problem

{describe the problem}

Fix

{describe the fix}

Why was it missed

{Some explanation why this issue might have been missed during normal development/testing cycle}

How can we avoid this

{if we don’t want to see this type of issues anymore what we should do to prevent}