BUG - fe-fpm-writer. Incorrect 'controlAggregation' applied when a new Object Page is added and FCL is enabled

[815are]

Steps to Reproduce

Steps to reproduce the behavior:

1. Use manifest.json with routing like:

"routing": {
            "config": {
                "flexibleColumnLayout": {
                    "defaultTwoColumnLayoutType": "TwoColumnsBeginExpanded",
                    "defaultThreeColumnLayoutType": "ThreeColumnsMidExpanded"
                },
                "routerClass": "sap.f.routing.Router"
            },
            "routes": [
                {
                    "pattern": ":?query:",
                    "name": "TripsList",
                    "target": [
                        "TripsList"
                    ]
                },
                {
                    "name": "TripsObjectPage",
                    "pattern": "Trips({TripsKey}):?query:",
                    "target": [
                        "TripsList",
                        "TripsObjectPage"
                    ]
                }
            ],
            "targets": {
                "TripsList": {
                    "type": "Component",
                    "id": "TripsList",
                    "name": "sap.fe.templates.ListReport",
                    "options": {
                        "settings": {
                            "contextPath": "/Trips",
                            "variantManagement": "Page",
                            "initialLoad": "Enabled",
                            "navigation": {
                                "Trips": {
                                    "detail": {
                                        "route": "TripsObjectPage"
                                    }
                                }
                            }
                        }
                    },
                    "controlAggregation": "beginColumnPages",
                    "contextPattern": ""
                },
                "TripsObjectPage": {
                    "type": "Component",
                    "id": "TripsObjectPage",
                    "name": "sap.fe.templates.ObjectPage",
                    "controlAggregation": "midColumnPages",
                    "options": {
                        "settings": {
                            "navigation": {},
                            "contextPath": "/Trips"
                        }
                    },
                    "contextPattern": "/Trips({TripsKey})"
                }
            }
        },

2. Add new object page to TripsObjectPage while FCL is enabled.
3. Problem - controlAggregation of new Object Page is beginColumnPages instead of endColumnPages

Expected results

controlAggregation of new Object Page is endColumnPages

Actual results

controlAggregation of new Object Page is beginColumnPages instead of endColumnPages

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}

[815are]

Fix - #3168