Improve error message for Flink process memory configuration

Originates from discussion in FLINK-19461.

Currently, all configuration failures will result in IllegalConfigurationException from JobManagerProcessUtils and TaskExecutorProcessUtils. The exception error messages do not refer to the process type (JM or TM), it can only become clear from the stack trace.

We can wrap main configuration calls with extra try/catch (TaskExecutorProcessUtils::processSpecFromConfig and JobManagerProcessUtils::processSpecFromConfigWithNewOptionToInterpretLegacyHeap) where IllegalConfigurationException is wrapped into another one which states type of the process (JM or TM).