Afaik this arguments are relevant for all serverless projects and we need to migrate it to shared FTR serverless config so it will be inherited and re-used by all serverless config files.
we probably can hardcode some values, but make it unique for project type, e.g.
Recently Search Team added Kibana server arguments (from project controller), required by project navigation tests.
https://github.com/elastic/kibana/blob/41850b67d181ab7d27503e3f7314754cbbce75da/x-pack/test_serverless/functional/test_suites/search/config.ts#L21-L33
Afaik this arguments are relevant for all serverless projects and we need to migrate it to shared FTR serverless config so it will be inherited and re-used by all serverless config files.
we probably can hardcode some values, but make it unique for project type, e.g.
The end goal is to have it in https://github.com/elastic/kibana/blob/41850b67d181ab7d27503e3f7314754cbbce75da/x-pack/test_serverless/shared/config.base.ts#L107 and make sure all the required updates are happening in shared base config.