Fix: biographical info not erased during personal data erasure (#64282)

[iflair]

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

Summary

This patch ensures the biographical information (user meta 'description') is removed
as part of the personal data erasure process.

What I changed

1. Added a personal data eraser function wp_user_personal_data_eraser() in wp-includes/user.php
   that deletes description user meta during erasure.
2. Registered the eraser via the wp_privacy_personal_data_erasers filter (wp-includes/default-filters.php).

Testing

• Applied the patch and verified description meta is removed when erasing personal data.
• (If you ran tests locally, list them here.)

Notes

• Original Trac diff: 64282.diff
• Author: @iFlairWebTechnologies

Please let me know if you'd like me to split the changes, add unit tests, or adjust any naming.

[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: @info@iflair.com.

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

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

[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

• The Plugin and Theme Directories cannot be accessed within Playground.
• 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.

[mindctrl]

6.7.0 wouldn't be accurate here, but we can't say for sure if it would be 7.0 or some other version. Typically in this case, the recommended tag is something like this (which gets changed when committed to whichever version is being targeted):

I'd update all the other @since tags in this PR to match.

Suggested change

	* @since 6.7.0
	* @since n.e.x.t