Describe the bug
I use Pods to create a list of date/times for today's date to display a status value. The display used to work perfectly for some time now. Today I noticed that the time appears to be displaying UTC rather than local time.
https://www.skydivesnohomish.com/contact/tandem-class-status/
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
In the example page URL it used to display 12pm to 7:30pm and now appears to be UTC times which are +7 hours.
Screenshots
If applicable, add screenshots to help explain your problem.

Please provide the version of Pods you are running:
Version: 2.7.13
Copy and paste your System Details Tools, Site Health, Info. Use the 'Copy Site Info to Clipboard' and paste the results over this line.
Copy and Paste the JSON Export from **Pods Admin, Migrate: Packages, Export** in WordPress admin here
Additional context
Add any other context about the problem here.
Possible Workaround
If you have discovered a workaround, please include it below.
Issue-Label Bot is automatically applying the label Type: Bug to this issue, with a confidence of 0.92. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Rolling back to Version 2.7.12 fixed the problem.

Most likely the same as #5402, though this one probably should be the canonical issue because I do believe it's directly related to UTC. This is reproduced locally and I'm looking into it.
Appears to be introduced here: https://github.com/pods-framework/pods/pull/5297/files
I believe this same problem in Pods Version 2.7.13 is showing up for a "Time" Field Type in admin and front end of my development site, delaying launch, https://www.mokshayoga.kenmick.com/ where Settings is local time Chicago DST = -5 UTC. This issue is resolved by downgrading to Pods Version 2.7.12.
Class start time of noon displays as 5pm, on clicking "edit" displays as 5pm, can adjust to noon, and on save reverts to 5pm.
see video: https://cl.ly/eff91a75e298
I think this problem is causing multiple reports yet to be noted as duplicates, including:
@sc0ttkclark This issue should not be in backlog. It's a major flaw around times and renders Pods broken when it comes to times. Whenever we're saving, we're having to update every record to add 10 hours (Australia +10) before saving – otherwise, the time ends up being wrong. This is required every-single-time a record is saved irrespective of whether the date/time has been altered. Please change this issue to priority!
Solved by #5409
Most helpful comment
Most likely the same as #5402, though this one probably should be the canonical issue because I do believe it's directly related to UTC. This is reproduced locally and I'm looking into it.