Using config manager to create component list instead of 'zwe'

[Gautham-coder]

Using configmgr to read config yaml for enabled components and check for start script in /instance/component-name/manifest, if both are present then add to component list, instead of zwe.

Solution:

1. Check for enabled components
2. for each enabled component check if the manifest.yaml exits either in <zowe.runtimeDirectory>/ components // or <zowe.extensionDirectory> /
3. if it exists then read item 'commands.start', if present then add the component to the component list.

Relates to issue: #110

[1000TurquoisePogs]

So far in my testing this is working for me.

[1000TurquoisePogs]

There was a previous question about if setting BPX AUTOCVT was going to help other code.

I added an env printout in zowe-common-c/libs/common.js which seems to be the earliest possible execution of configmg+zwe code.

It prints out like so

2024-06-18 11:14:56.421 <ZWELNCH:17237194> USER INFO ZWEL0069I Configuration is valid                                                               
2024-06-18 11:14:56.421 <ZWELNCH:17237194> USER INFO ZWEL0058I WORKSPACE_DIR is '/me/inst/stc/workspace-stc-initinstance7'                
e is _BPXK_AUTOCVT=ON                                                                                                                                  
e is JAVA_DUMP_TDUMP_PATTERN=SVCDUMP.D%y%m%d.T%H%M%S.&SYSNAME..%job                                                                                    
e is _CEE_DMPTARG=/proj/dumps                                                                                                                          
e is ROOT_DIR=/mydir                                                                                                         
e is _CEE_RUNOPTS=HEAPPOOLS(OFF) ENVAR("_CEE_ENVFILE=DD:STDENV") POS(ON)                                                                               
e is _=/mydir/bin/utils/configmgr                                                                                             
e is ZLDEBUG=OFF                                                                                                                                       
e is CONFIG=FILE(/me/inst/stc/zowe.yaml)                                                                                                     
e is ZWE_zowe_runtimeDirectory=/mydir                                                                                        
e is ZWE_CLI_PARAMETER_CONFIG=FILE(/me/inst/stc/zowe.yaml)                                                                                   
e is WORKSPACE_DIR=/me/inst/stc/workspace-stc-initinstance7                                                                                  
e is TZ=EST5EDT                                                                                                                                        
e is ZWE_CLI_PARAMETER_HA_INSTANCE={{ha_instance_id}}                                                                                                  
e is _CEE_ENVFILE=DD:STDENV                                                                                                                            
2024-06-18 11:14:56 <ZWELS:17237742> USER INFO (zwe-internal-start-prepare) Zowe version: v2.16.0      

Point is, yes looks like it does get set by launcher properly, as almost nothing else is set at this time except things the launcher set.