fix: validate absolute paths in filename

[anshumanv]

This PR contains a:

• bugfix
• new feature
• code refactor
• test update
• typo fix
• metadata update

Motivation / Use-Case

Fix #877

Breaking Changes

No

Additional Info

Do not allow absolute paths in filename schema, add min length of 1.

[codecov]

Codecov Report

Merging #878 (a60bde5) into master (e8c08a1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #878   +/-   ##
=======================================
  Coverage   91.28%   91.28%           
=======================================
  Files           6        6           
  Lines         792      792           
  Branches      214      214           
=======================================
  Hits          723      723           
  Misses         63       63           
  Partials        6        6           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e8c08a1...a60bde5. Read the comment docs.

[alexander-akait]

Thanks

[anshumanv]

@alexander-akait I realized there are more path options like chunkFilename and publicPath, should we add this check there too?

[alexander-akait]

publicPath can be any, for chunkFilename - yes

[anshumanv]

Got it, let me send a follow up 👍