Corrects AI plugin admin slug

[nimesh-xecurify]

Ensures the correct slug (ai-wp-admin) is used for the AI plugin's administration page link.

Trac ticket: https://core.trac.wordpress.org/ticket/65077

Trac ticket: https://core.trac.wordpress.org/ticket/65073

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @1178653+wordpress-develop-pr-bot[bot]@users.noreply.github.com.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

Core Committers: Use this line as a base for the props when committing in SVN:

Props nimeshatxecurify, audrasjb, jeffpaul, khokansardar.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[audrasjb]

This PR don't have any changeset @nimesh-xecurify :)

[nimesh-xecurify]

@audrasjb The wordpress-develop-pr-bot updated the build, which contained the changes. I guess I will need to somehow reference the new build from WordPress/gutenberg#77336

[audrasjb]

I still don't see any changeset in WordPress Core file ;)

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[jeffpaul]

A fix for this was already backported and will make it into 7.0 with the next sync: WordPress/gutenberg#77336 (comment)

[itzmekhokan]

Cross-reference for #65073: I opened an alternate PR (#11614) that applies the same behavioral fix but names the new constant AI_PLUGIN_PAGE_SLUG to match the upstream source-of-truth in Gutenberg (WordPress/gutenberg#77336). Using the upstream name means the built files will line up with what core receives at the next Gutenberg sync.

No objection to this PR's approach — linking so a committer can pick whichever naming they prefer; one of the two should be closed as a dup once that decision is made.