Harbor Should Ignore Commented ENV Keys

[mehrancodes]

When Harbor processes .env.example, it’s uncommenting lines like:

# DB_HOST=mariadb_1 # if you're using Sail
DB_HOST=127.0.0.1

We expect Harbor not to touch any commented-out env keys (the # DB_HOST line above).

Steps to Reproduce
1. Create or open a .env.example file with a commented-out variable (e.g., # DB_HOST=mariadb_1).
2. Run Harbor provisioning.
3. Notice that the previously commented line is now uncommented.

Expected Behavior
• Harbor should leave all commented lines as they are and only modify actual (uncommented) env keys.

Additional Context
• Any mention of # DB_HOST in .env.example (or similar) should remain commented after Harbor runs.
• This issue could affect any commented variables that the user wants to keep for reference but doesn’t currently need in their active configuration.