Split out z/OS package data by source

[pleia2]

When we first created our z/OS open source file with #5 , it was rather small and the software was scattered across various small outlets. This may still be the case for some (so we can keep a generic "other" file for z/OS), but we now have several sources which sometimes cause confusion and name collisions, and folks may now be looking to search those individually.

So the work done for #29 and #37 should be split out into separate files for each source, work which should begin in this repository. A follow-up issue will be created in the main tool so that anything we're automating gets split into those files too.

[pleia2]

@Princee215 & @aashish-khatri This one is rather high priority because of how out-dated the source has become. Let's sync up about it on Thursday to discuss how we want to pull this apart. /cc @arshPratap

[pleia2]

Note that #6 is related here too, since that was the initial commit. These should probably stay in this file, but we'll move everything else out to other files:

• ZOSOpentools.json (which is being done in added automation for z/OS open tools software-discovery-tool#124)
• IBM_Z_zOS.json for https://github.com/IBM/IBM-Z-zOS/ (these were added with ZOS_Software_List.json : Added pkgs from IBM-Z-zOS #38)

[pleia2]

I think we also want to split out the Rocket Software and Open Mainframe Project tools into their own files since there may be potential to automate these, so I'm proposing the following files:

• ZOS_OMP.json
• ZOS_Rocket_Software.json
• IBM_Z_zOS.json

I'm also going to remove all the z/OS Open Tools from the generic ZOS_Software_List.json because it's so out-dated at this point that I'm worried it's harmful, and work is being done to complete the automation for this, in its own new file.