ID 431586 - Update Input Handling - Default Inputs documentation to mention that there could be some caveats with overriding default_input(), as some nodes expect non-null inputs

Problem summary
Update Input Handling - Default Inputs documentation to mention that there could be some caveats with overriding default_input(), as some nodes expect non-null inputs

Documentation page

https://learn.foundry.com/nuke/developers/latest/ndkdevguide/split-and-execute/input.html#default-inputs

Expected behaviour
For the documentation to explain that sometimes overriding default_input() can cash Nuke to crash, as some nodes like the DeepRecolor node, expect a expect a non-null input

Actual behaviour
The documentation doesn't currently explain this caveat