Vector symbology batch update

[roya0045]

Fixes #6421 Fixes #6571 Fixes #6692 Fixes #6715 Fixes #6790 Fixes #6948

Proposal to update the vector symbology sections.

Images still need to be added.

[DelazJ]

@roya0045 Can you split up the PR so that 3.24 features are moved to another one? master is currently targeting 3.22LTR so until we set up a branch and release 3.22 docs, we cannot merge these

[roya0045]

@roya0045 Can you split up the PR so that 3.24 features are moved to another one? master is currently targeting 3.22LTR so until we set up a branch and release 3.22 docs, we cannot merge these

Sure thing!

[DelazJ]

@roya0045 I created a dedicated branch for 3.22 so you can open a PR with #6989 changes against master

[DelazJ]

Doing some review

[DelazJ]

The symbol referenced by the |mergedFeaturesSymbol| substitution does not exist yet in the repo. You need to create and load it (https://docs.qgis.org/testing/en/docs/documentation_guidelines/substitutions.html#usage)

[DelazJ]

Using "variable" is confusing as it might mean things like @.... "option" looks more appropriate to me.
This description does not look correct to me (or I don't understand it) and I feel like it contradicts the next paragraph. The scale is actually taken into consideration, leading to the size scaling. #6790 explains that well IMHO.

[DelazJ]

Suggested change

	use a width of 1mm to render a line. If the map is at a scale of 1: 10 000
	the line uses a width of 1mm to render, if the map is at a scale of 1: 10 000

We can also reuse the sentence in the GUI or the issue report.

[roya0045]

@DelazJ The embeded render doesn't have an icon, I'm not sure if I should remove the substitution or not.

[DelazJ]

@roya0045 no icon then no substitution possible. We will add one if ever the renderer has an icon (qgis/QGIS#42071)

[roya0045]

@roya0045 no icon then no substitution possible. We will add one if ever the renderer has an icon (qgis/QGIS#42071)

Good, should be fine now.

[DelazJ]

@roya0045 Sorry for the delay.

[github-actions]

The backport to release_3.22 failed:

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

stderr

error: could not apply 870768a9c1... 6692 base
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 docs/user_manual/working_with_vector/vector_properties.rst
[backport-6997-to-release_3.22 82928d92f0] 6421 base
 Author: Alex <roya0045@users.noreply.github.com>
 Date: Sun Oct 24 09:20:21 2021 -0400
 1 file changed, 17 insertions(+)
Auto-merging docs/user_manual/working_with_vector/vector_properties.rst
[backport-6997-to-release_3.22 f62872ddba] 6571 base
 Author: Alex <roya0045@users.noreply.github.com>
 Date: Sun Oct 24 09:23:52 2021 -0400
 1 file changed, 13 insertions(+)
Auto-merging docs/user_manual/style_library/symbol_selector.rst
CONFLICT (content): Merge conflict in docs/user_manual/style_library/symbol_selector.rst

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.22 release_3.22
# Navigate to the new working tree
cd .worktrees/backport-release_3.22
# Create a new branch
git switch --create backport-6997-to-release_3.22
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick f841693bcf790953b01565a10cd242ec1f1409c4,b595f36b6695207a515b743a1ba4a92f44ab39c3,870768a9c196ed075ff98b6fe4c4ffedfd7bb466,ea71b1cde6f33aec123cd43d3826a34366200e78,0a82e58611854b6fb49512d95e0f1df882ead796,05bcecb7113e9d8adb2dc4867198549dae85cb18,831086891250f7ab424d2df153ddc9f423145652,39c304247d0637fb112f36f0cf3b167e5ff30bd8,02880d02840954f5a2c6f77c44b46119ceec77fa,8e9e1e50c295473c4ec0104887e20519bf14a4a1,71d8b4df3be067de3dddf39f041a2344be71bd42,34babfe0ecd5e36055b9e09edd4a69a00ce1364b,88837eb1a9932fcd30fdde98306f3a59f9f42044,b9dc1863206e16a97d06d957bf82d9b49896d2e4,6f5c170107a208f1c8c6babac609668edc486801,47fe4fd9c5e1fac06a133cd7ec6d89e752d9ca79,3a27d7f45bffd9ca8a74c21ca3898b7872759083
# Push it to GitHub
git push --set-upstream origin backport-6997-to-release_3.22
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release_3.22

Then, create a pull request where the base branch is release_3.22 and the compare/head branch is backport-6997-to-release_3.22.