[launch_manager] Honor deployment_config.working_dir as the spawned process cwd

[eduard-moskalchuk]

What

The Launch Manager never applies a component's configured working_dir. The child process cwd is hard-coded to the executable's directory in changeCurrentWorkingDirectory() (chdir(dirname(executable_path))), and the working_dir value is dropped entirely on the way to the daemon.
As a result, applications that access files relative to their cwd (e.g. ./etc/file.txt) fail, because the cwd was <bin_dir> instead of the configured working_dir.

Acceptance Criteria (DoD)

Working directory specified in the deployment config is applied.

How

No response

[NicolasFussberger]

Thanks for the ticket @eduard-moskalchuk
Currently, this working_dir not being supported was noted here as a known limitation

lifecycle/score/launch_manager/docs/product_documentation/known_limitations.rst

Lines 36 to 37 in 78ddf71

	* The parameter ``deployment_config/working_dir`` is currently not supported
	and is ignored.

However, @TimoSteuerwaldETAS will resolve this in his next PR. So I'll assign the ticket to him.

[TimoSteuerwaldETAS]

@eduard-moskalchuk PR is ready and can be reviewed. See also link in the issue. :-)