onConflict config option does not apply to implicitly created functions

[GrantGryczan]

Practical example:

[TheMrZZ]

This is actually a non-trivial problem. To fix it correctly, the "implicitely created function" should take the conflict strategy of its parent, or the general one. However, I'd need to rewrite some critical parts of Sandstone (this is planned anyway). But I won't take that risk.

Therefore, I fixed it partially: it will always default to the general strategy if it is "throw", "replace", "ignore" or "warn", but it won't take the conflict strategy of the parent.