8301998: Update HarfBuzz to 7.0.1

[honkar-jdk]

This is a backport of HarfBuzz v7.0.1 changes commit#fc104420d8 and the original PR#12913

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8301998: Update HarfBuzz to 7.0.1

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk20u pull/20/head:pull/20
$ git checkout pull/20

Update a local copy of the PR:
$ git checkout pull/20
$ git pull https://git.openjdk.org/jdk20u pull/20/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 20

View PR using the GUI difftool:
$ git pr show -t 20

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk20u/pull/20.diff

[bridgekeeper]

👋 Welcome back honkar! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@honkar-jdk This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8301998: Update HarfBuzz to 7.0.1

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 2 new commits pushed to the master branch:

• 5138f5a: 8300692: GCC 12 reports some compiler warnings in bundled freetype
• e7e1b5f: 8303937: Corrupted heap dumps due to missing retries for os::write()

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (736e0036)

[honkar-jdk]

/integrate

[openjdk]

@honkar-jdk
Your change (at version 736e003) is now ready to be sponsored by a Committer.

[prrace]

/sponsor

[openjdk]

Going to push as commit cc4b7e6.
Since your change was applied there have been 2 commits pushed to the master branch:

• 5138f5a: 8300692: GCC 12 reports some compiler warnings in bundled freetype
• e7e1b5f: 8303937: Corrupted heap dumps due to missing retries for os::write()

Your commit was automatically rebased without conflicts.

[openjdk]

@prrace @honkar-jdk Pushed as commit cc4b7e6.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

[jianglizhou]

/integrate

[openjdk]

@jianglizhou The command integrate can only be used in open pull requests.