fix: correct control aggregation for object page when fcl is enabled

[815are]

Issue #3170

Scenario:

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.

Problem - controlAggregation of new Object Page is beginColumnPages instead of endColumnPages

Issue navigation was not passed to method getFclConfig

[changeset-bot]

🦋 Changeset detected

Latest commit: 6331383

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@sap-ux/fe-fpm-writer	Patch
@sap-ux/fiori-elements-writer	Patch
@sap-ux/fe-fpm-cli	Patch
@sap-ux/fiori-app-sub-generator	Patch
@sap-ux/repo-app-import-sub-generator	Patch
@sap-ux/generator-simple-fe	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[AlinaGovoruhina]

Config for controlAggregation fixed, change tested, changeset added.

[devinea]

Code changes are clear and covered by test.
changeset ✅

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud