fix: uncomment NEXT_PUBLIC_URL and NODE_TLS_REJECT_UNAUTHORIZED in the generated .env

[Ta5r]

What

This PR updates the .env file generation logic to ensure that NEXT_PUBLIC_URL and NODE_TLS_REJECT_UNAUTHORIZED are always included as an active (uncommented) entry. It also updates the corresponding test cases to reflect this change.

Why

Previously, NEXT_PUBLIC_URL and NODE_TLS_REJECT_UNAUTHORIZED were being commented out when they had a default value. Since this variables are crucial for frontend applications, ensuring it is always uncommented eliminates unnecessary setup issues.

Related Issue(s):

• Closes https://github.com/orgs/rtCamp/projects/141/views/1?pane=issue&itemId=96979705

How

• Updated access-functions.php: Modified the response of snapwp_helper_get_env_variables to include values to be passed to the reuired variables.
• Updated Generator.php: Modified the condition in prepare_variable() to prevent 0 (zero) value from throwing an InvalidArgumentException.
• Updated tests:
  • GeneratorTest.php
  • RestControllerTest.php

Screenshots

Checklist

• I have read the Contribution Guidelines.
• My code is tested to the best of my abilities.
• My code passes all lints (PHPCS, PHPStan, ESLint, etc.).
• My code has detailed inline documentation.
• I have added unit tests to verify the code works as intended.
• I have updated the project documentation accordingly.

[justlevine]

We should also update NODE_TLS_REJECT_UNAUTHORIZED so its uncommented + set to 0 in our access function.

[justlevine]

Love it - just need to adjust some of the generated comments (and the matching tests)