Steps to reproduce:

1. Import the host nested_lld_script_delay_not_resolved.yaml
2. Open Data collection -> Hosts -> nested-delay -> Discovery rules
3. Start the server
4. Execute the discovery rule L1 script

Result:
"L1 script" shows:

Cannot create item prototype "nested.calc_delay[svcA,{#SUB}]": Invalid update interval "{#DELAY}"..
Cannot create item prototype "nested.calc_delay[svcB,{#SUB}]": Invalid update interval "{#DELAY}"..

• nested.calc_delay is not copied into the discovered rules, so no items are created for it.
• nested.calc_ctrl and nested.calc_pdelay are copied ( {#PDELAY}is resolved to 30s / 1m) and their items (svcA,x / svcA,y / svcB,z) are created and collect data.

• The discovered rules themselves show no error.
• The error message ends with a double period.

Expected:
The item prototype is copied into each discovered LLD rule with "{#DELAY}" kept as is, and the items discovered by that rule get the resolved interval (45s, 2m, 90s), the same way {#PDELAY} works one level up. The update interval should only be validated once all LLD macros are resolved (when the item is created).

Affected fields: