Leading and trailing whitespace for values in starter.ini can break the system

[apolopena]

Describe the bug

Putting leading or trailing whitespace in a value in starter.ini can cause hard to track bugs
Ideally all leading or trailing whitespace should be removed from values when they are parsed but realistically for interim the leading and trailing whitespace values may just need to be trimmed after they are parsed.

Screenshots

Steps to reproduce

in starter.ini add some trailing whitespace to version=7.4 in the [PHP] section
The php version will now be invalid and will fall back to 'latest'

Expected behavior

Leading or trailing whitespace should not break the value

Additional information

This problem could happen in alot of places so it should probably be fixed in the parsing utility rather than everywhere a value is parsed. Although doing it this way would make the parsing function less 'multipurpose'.
Perhaps a flag can be passed to the function as a third argument that would preserve all whitespace.

See the parse_ini_value function in https://github.com/apolopena/gitpod-laravel-starter/blob/main/.gp/bash/utils.sh for the parsing utility function.

[apolopena]

Currently I dont have enough time to properly test this fix if I make the change in parse_ini_value.

So I am going to add a trim_external function to utils.sh and then just use it trim values after they are parsed.

Later as an optimization and when I have the time to test it. I will add a flag as a third argument to the parse_ini_value in utils.sh that will preserve all trailing and leading whitepspace.

Note:
Testing stuff like this is really time consuming because of how gitpod builds its docker images and the fact that parsing ini values is pretty much the core function of gitpod-laravel-starter.