Build/Test Tools: Update wp-prettier to 3.0.3 and refine ESLint ignore patterns

[Infinite-Null]

Trac ticket: #62935

Description

This PR updates the wp-prettier dependency from version 2.6.2 to 3.0.3 and refines the ESLint ignore patterns for better build management. The changes aim to fix the issues with lint:jsdoc and lint:jsdoc:fix scripts.

Changes proposed in this Pull Request

• Upgrade wp-prettier from 2.6.2 to 3.0.3 to resolve JS linting issues
• Update .eslintignore patterns to be more specific:
  • Add build-module and build-types directories
  • Replace /build with build for consistency
  • Add *.min.js pattern to ignore minified files
  • Update wp-includes JS ignore pattern

Testing Instructions

1. Run npm install to update dependencies
2. Run npm run lint:jsdoc to verify linting works
3. Run npm run lint:jsdoc:fix to verify auto-fixing works
4. Verify that build directories are properly ignored

Screenshots

[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.

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

Props ankitkumarshah.

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.