Implement a {{ current_user_email() }} Jinja macro on Preset Cloud

What is the problem or goal the end user is trying to solve or accomplish?

Admins would like to create dynamic RLS rules so that users are only able to see data associated with their email address.

How are they solving it currently?

This is possible using the {{ current_username() }} macro, but retrieving usernames is only possible through the REST API, and since this is Preset-specific it's not ideal to insert on the DB.

What is the recommended solution by the Customer?

Create a Jinja macro {{ current_user_email() }} so that admins can limit visibility only to content associated with the user's email address (on the DB level).