Case 1: Autoregistration ignores templates with matching item keys

Precondition: Zabbix 6.0; setup your configuration https://www.zabbix.com/documentation/current/en/manual/discovery/auto_registration#:~:text=new%20Zabbix%20proxy-,Configuration,-Specify%20server

Steps to reproduce:

• Create two templates e.g. test1 and test2 with an item with key "agent.ping"
• Simultaneously link both of these templates to e.g. test3
• Go to Configuration>Actions>Autoregistration actions
• Create a new action with operations:
  -) Add host
  -) Link to templates: {test3}
• Wait till a host will be created via the autoregistration process

Result: Host is created and the template is successfully linked. The host has two items with matching item keys.

Expected: Host shouldn't contain conflicting items/templates. The error should appear in the zabbix_server.log file regarding matching item keys.

Note: the same issue appears if hosts are discovered via the "Network discovery" process

Case 2: Autoregistration ignores templates with matching "discovery rule" and "item prototype" key

Precondition: Zabbix 6.0; setup your configuration https://www.zabbix.com/documentation/current/en/manual/discovery/auto_registration#:~:text=new%20Zabbix%20proxy-,Configuration,-Specify%20server

Steps to reproduce:

• Go to Configuration>Templates and create a template e.g. testa with a "discovery rule" key e.g. discovery and "item prototype" with key e.g.

  trap[ {#ID}]
  

• Full clone the template testa with the name e.g. testb
• Simultaneously link both templates (testa, testb) to e.g. testc
• Create a new action with operations:
  -) Add host
  -) Link to templates: {testc}
• Wait till a host will be created via the autoregistration process

Result: Host is created and the template is successfully linked. The host has two discovery rules and two item prototypes with matching item keys.
   
Expected: Host shouldn't contain conflicting discovery rules/item prototypes. The error should appear in the zabbix_server.log file regarding matching item keys.

Note: the same issue appears if hosts are discovered via the "Network discovery" process