Handle Bokeh 3.0 CDSView change

[bryevdv]

Starting with Bokeh 3.0, CDSView will automatically infer the correct ColumnDatSource to apply to, and therefore no longer has a source property. See

• Remove CDSView.source and infer the source from CDSView's parent bokeh/bokeh#11773

This PR adds an version check to explicitly switch appropriate behavior.

• Tests added / passed
• Passes pre-commit run --all-files

NOTE: just checking CI at this point, I still need to actually manually test with 3.0.0dev

[jrbourbeau]

Thanks @bryevdv -- just as a heads up there are a few known flaky tests, so if you see seemingly unrelated test failures in CI, that is most likely the cause

[bryevdv]

@jrbourbeau AFAICT everything is working fine with both 2.4.2 and 3.0.0dev

I am seeing an error message on exit with 3.0dev

ValueError: failed to validate DataRange1d(id='10668', ...).start: expected an element of either Float, Datetime or TimeDelta, got {'$type': 'number', 'value': 'nan'}
bokeh.server.protocol_handler - ERROR - error handling message
 message: Message 'PATCH-DOC' content: {'events': [{'kind': 'ModelChanged', 'model': {'id': '10702'}, 'attr': 'end', 'new': {'$type': 'number', 'value': '-inf'}}], 'references': []}
 error: ValueError("failed to validate DataRange1d(id='10702', ...).end: expected an element of either Float, Datetime or TimeDelta, got {'$type': 'number', 'value': '-inf'}")

But that seems like something to handle in a separate issue

[bryevdv]

@jrbourbeau I did dig into the three failed tests, all "macos, not ci1" tests and all with a few failures related to reconnection and/or timeouts. I don't think they pertain to anything Bokeh-related but any guidance is welcome.

[jrbourbeau]

Thanks @bryevdv, those tests are definitely unrelated to the changes here

[jrbourbeau]

FWIW I'm running the full CI suite against the development version of bokeh over in #5648 to see what happens

[bryevdv]

Thanks @jrbourbeau !