Fix docs build: resolve collocate_data ambiguity on Julia 1.12

[ChrisRackauckas-Claude]

The build / Build and Deploy Documentation job on main fails on Julia 1.12. The first @example collocation_cp block in docs/src/neural_ode_training.md errors with:

UndefVarError: `collocate_data` not defined in `Main.__atexample__named__collocation_cp`
Hint: ... two or more modules export different bindings with this name, resulting in ambiguity.
Hint: a global variable of this name also exists in DiffEqFlux.
Hint: a global variable of this name also exists in DataCollocations.

The block does both using DiffEqFlux and using DataCollocations, and both modules export collocate_data. On Julia 1.12 an unqualified reference to a name exported by two using-ed modules is an ambiguity error rather than silently resolving to one. The first block failing cascaded to every later block on the page (du/u/prob_neuralode undefined), so makedocs terminated with an [:example_block] error.

Fix

Import collocate_data explicitly from DataCollocations (alongside the already-explicit EpanechnikovKernel):

-using DataCollocations
-using DataCollocations: EpanechnikovKernel
+using DataCollocations: collocate_data, EpanechnikovKernel

This makes the binding unambiguous regardless of DiffEqFlux re-exporting the same name. Only neural_ode_training.md imports DiffEqFlux, so no other page is affected.

Local verification (Julia 1.12.6, real DiffEqFlux + DataCollocations)

• OLD import reproduces the exact CI UndefVarError ambiguity.
• NEW import resolves collocate_data to DataCollocations.collocate_data (verified parentmodule).
• The examples actual collocate_data(data, tsteps, EpanechnikovKernel())call executes and returnsdu/uof size(2, 300)`.

Please ignore until reviewed by @ChrisRackauckas