Add Name-Value Pair (NVP) area to the Dumps captured in the file system for the z/TPF Debugger

We'd like the Name-Value Pair (NVP) area added to the Dumps captured in the file system for the z/TPF Debugger because with increased use of Name-Value Pairs for saving information useful in Troubleshooting and for Realtime Runtime Metrics Collection (RTMC), the NVP Area is becoming increasingly important to our application developers to troubleshoot test and production issues.  All our legacy Communications packages, newer Communications packages such as REST Services, and some TPF applications have been updated to store Input Message/Inbound Data payload, Communications path, Communcations application routing information, embedded Service for Structured Data, End to End tracking ID, REST Operation ID, User Identifier, User Role, User Location, and other useful information.   The NVP area now provides a consolidated view of what the message was, how the message came into the system, who drove the message into the system, and what it was trying to do which is extremely useful in troubleshooting producton issues.

Another valuable addition for dump troubleshooting would be to allow ZCDNV to display a configurable number of NVPs on the Dump messages displayed on the prime cras console rather than the current limit of 3 NVPs.  This is extremely useful especially since the majority of Dumps are NODUMP'd in our TPF systems and the NVPs on the dump messsages allow for better pattern recognition with the above NVPs to determine if the dumps are impacting only one or many Comms paths, Users, Locations, etc...