[Bug] Add embedded layers to keyValueConfig object

[mind84]

Embedded layers are not taken into account when Lizmap requires the the key value configuration for attribute table display.

I did a little refactoring on handling embedded layers during projects loading (it's in a separated commit, but it is strictly related to this bug)

Funded by Faunalia

[mind84]

Backport in 3.8, if possible.

Thanks

[Gustry]

Sorry, I just renamed the project, to not only cover "editing capabilities" in #4846. Can you rebase and update the project name ?

[mind84]

Can you rebase and update the project name ?

I think is good now

[3liz-bot]

The backport to release_3_8 failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 22a0571b0... add embedded layers to keyValueConfig object
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"

stdout

Auto-merging lizmap/modules/lizmap/lib/Project/QgisProject.php
[backport-4847-to-release_3_8 50399276d] refactoring of embedded projects referencing during projects loading
 Author: Riccardo Beltrami <riccardo.beltra@gmail.com>
 Date: Mon Oct 7 12:01:54 2024 +0200
 1 file changed, 38 insertions(+), 40 deletions(-)
Auto-merging lizmap/modules/lizmap/lib/Project/QgisProject.php
CONFLICT (content): Merge conflict in lizmap/modules/lizmap/lib/Project/QgisProject.php

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release_3_8 release_3_8
# Navigate to the new working tree
cd .worktrees/backport-release_3_8
# Create a new branch
git switch --create backport-4847-to-release_3_8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 56745f1fc169566fb3e2e61e2cb4afb9d9821068,22a0571b0048e1d0ae0e520e7b7164012ac7b1a4
# Push it to GitHub
git push --set-upstream origin backport-4847-to-release_3_8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release_3_8

Then, create a pull request where the base branch is release_3_8 and the compare/head branch is backport-4847-to-release_3_8.