Fix: Exception when parsing .env with comments

[evansims]

Changes

This resolves an issue with parsing .env files that contain lines without standard key-value strings, such as # Comments.

References

Resolves #394

Contributor Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 code of conduct

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (507f5a7) 100.00% compared to head (60e6cc0) 100.00%.

Additional details and impacted files

@@             Coverage Diff             @@
##                main      #395   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity       496       496           
===========================================
  Files             31        31           
  Lines           1271      1271           
===========================================
  Hits            1271      1271           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/Configuration.php	100.00% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[cwp-sheal]

Could I ask why there is manual processing of .env files?

Doing this causes problems where:

1. I use comments in an env file
2. If I don't put them in the .env and instead us OS level environment variables (docker)