IBX-9030: Add content name pattern examples

[adriendupuis]

Question	Answer
JIRA Ticket	IBX-9030
Versions	master, 4.6 (3.3?)
Edition	All

Add several content name pattern examples, from simple to advanced, an a notice about special characters (encountered in IBX-8897)

Preview: https://ez-systems-developer-documentation--2513.com.readthedocs.build/en/2513/administration/content_organization/content_types/#content-type-metadata

Checklist

• Text renders correctly
• Text has been checked with vale
• Description metadata is up to date
• Redirects cover removed/moved pages
• Code samples are working
• PHP code samples have been fixed with PHP CS fixer
• Added link to this PR in relevant JIRA ticket or code PR

[mnocon]

Thank you, I like the examples!

One comment about the special usage, because I think it can be made clearer.

[mnocon]

Suggested change

	**Notice that you won't be able to obtain a vertical bar `|` or parentheses in the generated names as they are special characters.**
	**The grouping`(`, `)` symbols used together are treated as special keywords and can only be used together as such, without the possibility to use them as standard characters. **

Nitpick: I believe you can obtain them in the generated names - if the fields contain them, they just cannot be part of the pattern in other meaning than the "special one"

I did some tests and it looks like you can use the | symbol in its standard meaning - only the grouping is not allowed.

CT settings:

Content:

[adriendupuis]

@mnocon
OK for removing pipe and being clearer about parentheses.
I'm adding an example of what could go wrong so one could even search for "EZMETAGROUP_0" and find this explanation. What do you think about the following phrasing?:

Suggested change

	**Notice that you won't be able to obtain a vertical bar `|` or parentheses in the generated names as they are special characters.**
	**Notice that the grouping parentheses (characters `(`and `)`) are always treated as special characters, and can't be used as standard characters (unexpected text would appear in between like `(EZMETAGROUP_0)`).**

[Sztig]

After a small discussion with @alongosz it looks like the () should not be parsed outside angle brackets <> and it might be a regression, I will check on 3.3 where it was reported to work as intended and if the bug not happens there then I will proceed with it as a new bug. Maybe we should wait with pushing the documentation till it is resolved.