Enhance user magictag

[JoryHogeveen]

Description

Currently the {@user.##} magic tag is quite limited to the WP_User object only.
This won't properly support multiple metedata values and also doesn't consider the a possible User Pod.
This PR fixes this by fixing two things:

• pods_v() > Proper order of getting user properties or metadata
• pods_evaluate_tag() > If a user Pod exists, it will run the tag through this Pod first.

Related GitHub issue(s)

Fixes #7150

Changelog text for these changes

PR checklist

• I have tested my own code to confirm it works as I intended.
• My code follows the WordPress Coding Standards.
• My code follows the WordPress Inline Documentation Standards.
• My code includes automated tests for PHP and/or JS (if applicable).

[what-the-diff]

PR Summary

• Improved Handling of Variables in Data Logic
  The code has been enhanced to better handle variables, specifically the 'role' and 'var' variables, in our data structure. This improves the flexibility and robustness of the data processing system.
• Enhanced Functionality for User Special Magic Tag
  The system now incorporates additional logic to manage special user triggers. These improvements to the 'pods_evaluate_tag' function enables our system to more easily manage specific user-related activities.

[JoryHogeveen]

Needs doc update: https://docs.pods.io/displaying-pods/magic-tags/special-magic-tags/#Usage_and_Caveats

While not entirely invalid, this bottom part isn't 100% correct in regards to metadata (whether a user pod exists or not)