move pointer tag common utility functions to xml_utils and add pointer tag support in HTML XBlock

[ttqureshi]

• resolves: Create xml_utils and add support for pointer tag utilities in the HTML XBlock. public-engineering#435

The utility functions in xml_utils are derived from the XmlMixin class in the edx-platform. We are only retaining the functionality related to pointer tag parsing, ensuring that Extracted XBlocks can be exported and imported in the pointer tag format without any issue.

Here are the detailed references:

Utility Functions	References
name_to_pathname	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L22
is_pointer_tag	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L30
serialize_field	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L54
deserialize_field	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L71
own_metadata	https://github.com/openedx/edx-platform/blob/master/xmodule/modulestore/inheritance.py#L335
apply_pointer_attributes	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L499-L506
format_filepath	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L422
file_to_xml	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L178
load_file	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L188
load_definition_xml	https://github.com/openedx/edx-platform/blob/master/xmodule/xml_block.py#L412
EdxJSONEncoder	https://github.com/openedx/edx-platform/blob/master/openedx/core/lib/json_utils.py

[openedx-webhooks]

Thanks for the pull request, @ttqureshi!

This repository is currently maintained by @openedx/axim-engineering.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[farhan]

Seems good, just minor doc improvements

[farhan]

Good work ⭐

[farhan]

@ttqureshi Please mention, how did you do its manual testing

[ttqureshi]

TESTING NOTES:
I created a course that contained various HTML blocks (Text, IFrame, etc.). Then, I exported the course to verify that the definitions were being exported in the expected pointer tag format. To confirm that the HTML pointer tags were generated correctly, I compared my course export with the export of the built-in HTML block—both manually and using this script.

After that, I imported the course (which included the pointer tag definitions of the HTML block), and all HTML blocks were initialized correctly, as expected.

[ttqureshi]

@kdmccormick this PR is up for your reivew. Please take a look.

[kdmccormick]

Could you please add type annotations for every argument and return value?

Otherwise, looks good!

[ttqureshi]

PR is up for the final pass.