Standardize common job param names

Currently if you use the drmaa job runner plugin, you specify the native specification using the `nativeSpecification` param (this name comes directly from the drmaa library). However, pulsar destinations use the `submit_native_specification` param.

This distinction complicates dynamic rules and is sure to result in configuration mistakes, especially prior to having config validation.

In this case, the pulsar naming is better.

Search the job runner configuration and destination handling for the `nativeSpecification` and `submit_native_specification` parameters, starting with the DRMAA plugin and Pulsar destinations. Standardize the DRMAA parameter to the Pulsar naming where appropriate, and verify that dynamic rules and configuration references use one consistent name.

Written by the indexing model from the issue text.