Don't force full calculation of layer extent when cloning layers

[nyalldawson]

This can be extremely expensive to calculate for some sources, so just clone whatever information we currently have available instead of force calculating the full exact extent.

[github-actions]

🪟 Windows builds ready!

Windows builds of this PR are available for testing here. Debug symbols for this build are available here.

(Built from commit 6c45977)

[qgis-bot]

The backport to release-3_34 failed:

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

stderr

error: could not apply 6c459778788... Don't force full calculation of layer extent when cloning layers
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".

stdout

Auto-merging src/core/qgsmaplayer.cpp
CONFLICT (content): Merge conflict in src/core/qgsmaplayer.cpp
Auto-merging src/core/vector/qgsvectorlayer.cpp

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_34 release-3_34
# Navigate to the new working tree
cd .worktrees/backport-release-3_34
# Create a new branch
git switch --create backport-56434-to-release-3_34
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 6c45977878868a9b607817e8a4698ceb98aa2968
# Push it to GitHub
git push --set-upstream origin backport-56434-to-release-3_34
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-3_34

Then, create a pull request where the base branch is release-3_34 and the compare/head branch is backport-56434-to-release-3_34.