options: Add path_t and use it for hdri

[mwestphal]

No description provided.

[github-actions]

You are modifying libf3d public API! ⚠️Please update bindings accordingly⚠️!
You can find them in their respective directories: python, java, webassembly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.80%. Comparing base (c7f7a99) to head (14099e5).
Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2045      +/-   ##
==========================================
- Coverage   95.80%   95.80%   -0.01%     
==========================================
  Files         128      128              
  Lines       10488    10505      +17     
==========================================
+ Hits        10048    10064      +16     
- Misses        440      441       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Meakk]

Any reason to not use std::filesystem::path?

[mwestphal]

Any reason to not use std::filesystem::path?

Im using std::filesystem::path already, inside of path_t. Its required to be done like this as std::filesystem::path is not part of the variant API. Adding a new type to the variant API is a possibility but I'd rather not.

[mwestphal]

nevermind you are right @Meakk , I can use std::filesystem::path directly

[mwestphal]

actually a valid approach compared to #2046