refactor: Remove bok-choy and xblockutils (use xblock.utils instead) packages

[farhan]

Description

1. Removed xblock utils package and migrated to xblock package utils:
   • Replace xblockutils.* imports with xblock.utils.* imports
   • ticket: Remove xblockutils package #356
2. Removed bok-choy packages:
   • Removed bok-choy package and its relevant test cases
   • ticket: Remove bok-choy usage #354
3. Updated python requirements

Breaking change in tests

There is no breaking change in the xblock feature in the implementation of this PR
As we have parted ways with the bok-choy library this PR is removing all the integrating test cases along with the base test classes because they are linked with the library.

Notes

Resolves #356
Resolves #354

[Agrendalath]

@farhan, this should define a minimum version for the XBlock dependency in the requirements/base.in.

We should bump the major version here if we do not provide the fallback import from xblockutils. We should also clearly state which of the edx-platform named releases are compatible with this new version.

[Agrendalath]

@farhan, why are we removing integration tests? Are we going to replace them with something else?

[farhan]

@farhan, why are we removing integration tests? Are we going to replace them with something else?

@Agrendalath We are removing bok-choy integration tests because the library has been deprecated.

Bok-choy integration test has not been copied from xblock-utils to xblock/tests/utils

due to which the repositories that are using the base test classes of xblock/integration/tests are breaking.

We are already planning to remove bok-choy test cases, so covering it in this pr as well.
relevant ticket: #354

[salman2013]

@farhan few test cases are failing like
https://github.com/openedx/xblock-drag-and-drop-v2/actions/runs/6545659095/job/17774598693?pr=357

[farhan]

@Agrendalath
I have completed my implementation.
I have removed all the things related to the integration test as all of them are linked to the Bok-choy test cases library.
I have removed the relevant configuration and docs related to integration tests as well. Please guide should we remove all of it as we don't have any plan in the pipeline to write integration tests again using other library.

We should also clearly state which of the edx-platform named releases are compatible with this new version.

I have added the details in the change log, should we state this change on some other place as well?

[Agrendalath]

@farhan

I have removed all the things related to the integration test as all of them are linked to the Bok-choy test cases library.
I have removed the relevant configuration and docs related to integration tests as well. Please guide should we remove all of it as we don't have any plan in the pipeline to write integration tests again using other library.

What do you mean by "all of it"?

I have added the details in the change log, should we state this change on some other place as well?

This is a breaking change, so we should indicate this in the commit, PR's name + description, and the changelog. Please take a look at #318 for an example of how we have been doing it.

Also, I wonder if xblock[django]==1.8.1 really is incompatible with older named releases. I don't see any breaking changes in its changelog or release notes.

[farhan]

What do you mean by "all of it"?

@Agrendalath I want to ask please verify all the removal done in this PR seems right to you

Also, I wonder if xblock[django]==1.8.1 really is incompatible with older named releases. I don't see any breaking changes in its changelog or release notes.

That's true there is no breaking change in xblock release v1.8.0 and v1.8.1

[farhan]

@Agrendalath
PR (Pull Request) is now ready for your review. I have also made necessary updates to the description, specifically addressing the breaking change. Your prompt review of these changes would be greatly appreciated.
cc: @feanil

[farhan]

@Agrendalath Addressed all the requested changes.
PR is available for next pass

[Agrendalath]

@farhan, thanks for working on this!

👍

• I tested this: checked that the XBlock is working correctly with Nutmeg and master versions of the devstack
• I read through the code
• I checked for accessibility issues: n/a
• Includes documentation: n/a