Fix REX provider type (#4434)

* Fix REX provider type
** Package Action: foreman_remote_execution -> app/views/templates/script/package_action.erb
** Power Action: foreman_remote_execution -> app/views/templates/script/power_action.erb
** Puppet Run Once: foreman_puppet -> app/views/templates/script/puppet_run_once.erb
** Service Action: foreman_remote_execution -> app/views/templates/script/service_action.erb
* Salt: No change in "guides/common/modules/proc_running-salt.adoc" but
  looked into this issue via PR 219 in foreman_salt. (Untested but
  verified that the templates are currently called "Salt Run function - SSH default".
* Clicking "Run Puppet once" in WebUI really causes REX to start a job
  that uses the "Puppet Run Once - Script Default" template.
  Tested on Foreman 3.16
* Use canceled in favor of cancelled
  "guides/common/modules/con_host-substatus-overview.adoc" remains
  unchanged because the wording seems to come from the WebUI.
  This makes vale happy.

Fixes #4415 (Rename REX provider)
Fixes #4192 (Rename Puppet Run Once template)

(cherry picked from commit dfad7d7)

Author: maximiliankolb

guides/common/modules/proc_decreasing-performance-impact-of-the-pull-based-rex-transport.adoc

@@ -15,7 +15,7 @@ This also depends on actual job workload, as some jobs are causing additional lo
 To avoid this, configure your {ProjectServer} and {SmartProxyServer} with the following parameters:
 
 * MQTT Time To Live {endash} Time interval in seconds given to the host to pick up the job before considering the job undelivered
-* MQTT Resend Interval {endash} Time interval in seconds at which the notification should be re-sent to the host until the job is picked up or cancelled
+* MQTT Resend Interval {endash} Time interval in seconds at which the notification should be re-sent to the host until the job is picked up or canceled
 * MQTT Rate Limit {endash} Number of jobs that are allowed to run at the same time.
 You can limit the concurrency of remote execution by tuning the rate limit which means you are going to put more load on {Project}.
 

guides/common/modules/proc_including-power-actions-in-templates.adoc

@@ -12,5 +12,5 @@ This procedure prevents {Project} from interpreting the disconnect exception upo
 +
 [source, ruby]
 ----
-<%= render_template("Power Action - SSH Default", :action => "restart") %>
+<%= render_template("Power Action - Script Default", :action => "restart") %>
 ----

guides/common/modules/proc_running-puppet-once-using-ssh.adoc

@@ -10,6 +10,6 @@ Assign the proper job template to the _Run Puppet Once_ feature to run Puppet on
 . Edit remote execution settings on {Project}:
 .. In the {ProjectWebUI}, navigate to *Administer* > *Remote Execution Features*.
 .. Select the `puppet_run_host` remote execution feature.
-.. Assign the `Run Puppet Once {endash} SSH Default` job template.
-. To run Puppet on hosts, execute a remote job and select category `Puppet` and template `Run Puppet Once - SSH Default`.
+.. Assign the `Puppet Run Once {endash} Script Default` job template.
+. To run Puppet on hosts, execute a remote job and select category `Puppet` and template `Puppet Run Once - Script Default`.
 Alternatively, click *Run Puppet Once* in the *Schedule Remote Job* drop down menu on the host details page.

guides/common/modules/ref_customizing-job-templates.adoc

@@ -11,8 +11,8 @@ The following template combines default templates to install and start the *ngin
 
 [source, ruby]
 ----
-<%= render_template 'Package Action - SSH Default', :action => 'install', :package => 'nginx' %>
-<%= render_template 'Service Action - SSH Default', :action => 'start', :service_name => 'nginx' %>
+<%= render_template 'Package Action - Script Default', :action => 'install', :package => 'nginx' %>
+<%= render_template 'Service Action - Script Default', :action => 'start', :service_name => 'nginx' %>
 ----
 
 The above template specifies parameter values for the rendered template directly.
@@ -21,7 +21,7 @@ For example, you can use the following syntax:
 
 [source, ruby]
 ----
-<%= render_template 'Package Action - SSH Default', :action => 'install', :package => input("package") %>
+<%= render_template 'Package Action - Script Default', :action => 'install', :package => input("package") %>
 ----
 
 With the above template, you have to import the parameter definition from the rendered template.

guides/common/modules/ref_remote-execution-settings.adoc

@@ -47,10 +47,10 @@ Restart of the `dynflowd/{project-context}-tasks` service is required.
 You can override this per host by setting the `remote_execution_cleanup_working_dirs` parameter.
 | *Cockpit URL* | | Where to find the Cockpit instance for the Web Console button.
 By default, no button is shown.
-| *Form Job Template* | Run Command - SSH Default | Choose a job template that is pre-selected in job invocation form.
+| *Form Job Template* | Run Command - Script Default | Choose a job template that is pre-selected in job invocation form.
 | *Job Invocation Report Template* | Jobs - Invocation report template | Select a report template used for generating a report for a particular remote execution job.
 | *Time to pickup* | 86400 | Time in seconds within which the host has to pick up a job.
-If the job is not picked up within this limit, the job will be cancelled.
+If the job is not picked up within this limit, the job will be canceled.
 Applies only to pull-mqtt based jobs.
 Defaults to one day.
 |====