Add normalized contact data for anonymous users

[RabbiIslamRony]

PR Type

What kind of change does this PR introduce?

• Bugfix
• Security fix
• Improvement
• New Feature
• Refactoring (no functional changes, no api changes)
• Build related changes
• Text changes
• Other... Please describe:

Description

Main issue

Directorist extensions currently receive a WP_User only for registered visitors. A true guest flow has no reusable Core contract for carrying a sanitized email and display name, so extensions such as Booking can end up creating a WordPress account only to obtain contact data. That contradicts the expected guest-booking behavior and can trigger unwanted account emails.

What changed

• Added directorist_get_user_contact() for registered and anonymous contacts.
• Registered users resolve from WP_User or user ID.
• Anonymous callers can supply sanitized fallback email and name values.
• Added the directorist_user_contact filter for extension-specific adjustments.

How to test

1. Check out this Core PR together with the companion Booking PR listed below.
2. Run:
   wp eval '$contact = directorist_get_user_contact( 0, [ "email" => "guest@example.com", "name" => "Guest User" ] ); print_r( $contact );'
3. Confirm the result contains id => 0, guest@example.com, and Guest User.
4. Call the helper with a real user ID and confirm it returns that user's saved email and display name instead of the fallback.
5. Complete the guest-booking test from the companion PR and confirm no WordPress user is created.

Dependency / companion PR

• Directorist Booking PR: https://github.com/sovware/directorist-booking/pull/54

Any linked issues

• Client issue: https://team.sovware.com/support/directorist/3257
• Support conversation: https://secure.helpscout.net/conversation/3426004357/6295
• Companion Booking change fixes the reported guest-account, confirmation refresh, and field-icon problems.

Checklist

• My code follows the WordPress coding standards

[RabbiIslamRony]

Replaced by #2977 from a same-repository branch so the pull_request_target PHPCS workflow can safely check out and test the code. The implementation is unchanged.