chore: fix depr warning by updating import: xblockutils -> xblock.utils

[kdmccormick]

Context: openedx/XBlock#675

Fixes some edx-platform warnings:

2024-01-09 14:45:42,875 WARNING 289 [py.warnings] [user None] [ip None] warnings.py:109 - /openedx/venv/lib/python3.8/site-packages/poll/poll.py:40: DeprecatedPackageWarning: Please use import xblock.utils.publish_event instead of xblockutils.publish_event because the 'xblock-utils' package has been deprecated and migrated to within 'xblock' package. 
  from xblockutils.publish_event import PublishEventMixin

2024-01-09 14:45:42,875 WARNING 289 [py.warnings] [user None] [ip None] warnings.py:109 - /openedx/venv/lib/python3.8/site-packages/poll/poll.py:41: DeprecatedPackageWarning: Please use import xblock.utils.resources instead of xblockutils.resources because the 'xblock-utils' package has been deprecated and migrated to within 'xblock' package. 
  from xblockutils.resources import ResourceLoader

2024-01-09 14:45:42,875 WARNING 289 [py.warnings] [user None] [ip None] warnings.py:109 - /openedx/venv/lib/python3.8/site-packages/poll/poll.py:42: DeprecatedPackageWarning: Please use import xblock.utils.settings instead of xblockutils.settings because the 'xblock-utils' package has been deprecated and migrated to within 'xblock' package. 
  from xblockutils.settings import ThemableXBlockMixin, XBlockWithSettingsMixin

Uses a try-catch for backwards compatibility with pre-Quince versions
of xblock and xblockutils

Bumps version from 1.13.0 to 1.13.1

Resolves #114.

[Agrendalath]

Thanks for preparing this, @kdmccormick!

One request - could we make this change backward-compatible, as, e.g., we did here (ref)?

We won't need these fallbacks in tests, though.

[kdmccormick]

Sure thing @Agrendalath . Ready for another look.

[Agrendalath]

@kdmccormick:

1. It seems that the Selenium test mixins were not moved to the XBlock package. Should we remove Selenium tests, as we did in other repos?
2. If we decide to go with the approach from the previous point, we should replace xblock-utils with XBlock[django] in requirements/base.in.

[kdmccormick]

Good questions @Agrendalath . I wasn't aware that not all modules were copied from xblockutils to xblock.utils.

I see the justification for removing base_test.py is that bok-choy is deprecated, but it seems like xblock-poll uses base_test.py for integration testing without actually relying on bok-choy at all. The integration tests seem to be working fine in this repository and I'd hate to remove them for no reason. I'm wondering now whether it was a mistake to drop base_test.py. What do you think?

[bradenmacdonald]

It looks like base_test.py is still useful yep, as it can be used for "plain" selenium integration tests, without any bok-choy. In fact there's no code related to bok-choy in that file that I can see.

My suggestion is that since base_test.py is so tightly coupled with workbench, we move it into the xblock-sdk repo and combine it with test_utils.py which seems to have related functionality.

[farhan]

@kdmccormick its under discussion here
openedx/xblock-sdk#345 (comment)

[kdmccormick]

@bradenmacdonald and @Agrendalath : @farhan dug in and found that SeleniumXBlockTest was actually using bok-choy's WebAppTest as a base, so it seems that it was right to remove it instead of pulling it into XBlock.

Unless you have any objections, I'll remove this XBlock's selenium tests and update requirements/base.in to point at XBlock[django].

[kdmccormick]

This ended up being more work than I'm able to take on right now. I'm going to add some notes to #114 and close this. Feel free to re-use this PR in the future if that's helpful.