Simplify foremanctl attribute

"installer-foremanctl" is much longer and "foremanctl" has a broader
scope applicabble to other containerization contexts than just installer

Author: aneta-petrova

guides/common/assembly_planning-project-server-installation.adoc

@@ -16,6 +16,6 @@ ifeval::["{mode}" == "connected"]
 include::modules/ref_ipv6-and-ipv4-requirements.adoc[leveloffset=+1]
 endif::[]
 
-ifndef::installer-foremanctl[]
+ifndef::foremanctl[]
 include::modules/con_aws-requirements.adoc[leveloffset=+1]
 endif::[]

guides/common/assembly_preparing-environment-for-project-server-installation.adoc

@@ -6,6 +6,6 @@ include::modules/proc_opening-required-ports.adoc[leveloffset=+1]
 
 include::modules/proc_verifying-dns-resolution.adoc[leveloffset=+1]
 
-ifndef::installer-foremanctl[]
+ifndef::foremanctl[]
 include::modules/proc_preparing-for-using-external-databases.adoc[leveloffset=+1]
 endif::[]

guides/common/modules/con_planning-project-server-installation.adoc

@@ -5,7 +5,7 @@
 
 Review the following guidelines, requirements, and considerations before proceeding with the installation. 
 
-ifdef::installer-foremanctl[]
+ifdef::foremanctl[]
 :FeatureName: The `foremanctl` installer
 include::snip_technology-preview.adoc[]
 endif::[]

guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc

@@ -35,7 +35,7 @@ If you intend to provision hosts in an IPv6 network, the following requirements
 
 * Deploy an external DHCPv6 server and configure it manually to communicate with the network boot process and to manage IP address assignment because {Project} cannot integrate with a DHCPv6 server and manage its configuration.
 For more information about DHCPv6 server configuration, see {ProvisioningDocURL}options-in-unmanaged-dhcpv6[Options in unmanaged DHCPv6] in _{ProvisioningDocTitle}_.
-ifndef::installer-foremanctl[]
+ifndef::foremanctl[]
 * Configure {Project} for UEFI HTTP boot provisioning.
 Although {Project} provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the UEFI HTTP Boot provisioning is the only tested and certified provisioning workflow.
 For more information, see xref:configuring-for-uefi-http-boot-provisioning-in-an-ipv6-network_{context}[].
@@ -45,6 +45,6 @@ endif::[]
 ifdef::satellite[]
 * link:https://access.redhat.com/solutions/5045841[_How do I disable the IPv6 protocol on Red Hat Satellite and/or Red Hat Capsule server?_ in Red Hat Knowledgebase]
 endif::[]
-ifndef::installer-foremanctl[]
+ifndef::foremanctl[]
 * xref:adding-a-default-http-proxy_{context}[]
 endif::[]

guides/common/modules/ref_system-requirements.adoc

@@ -58,7 +58,7 @@ ifndef::foreman-deb[]
 For more information about configuring system locale in {EL}, see {RHELDocsBaseURL}9/html/configuring_basic_system_settings/assembly_changing-basic-environment-settings_configuring-basic-system-settings#proc_configuring-the-system-locale_assembly_changing-basic-environment-settings[Configuring the system locale] in _{RHEL}{nbsp}9 Configuring basic system settings_.
 endif::[]
 
-ifndef::installer-foremanctl[]
+ifndef::foremanctl[]
 * If you use an external identity provider in your deployment, ensure the provider did not create the following user accounts on the system.
 These user accounts can cause conflicts with the local users that {ProductName} creates:
 ** `{apache-user}`
@@ -78,7 +78,7 @@ ifeval::["{context}" == "{project-context}"]
 endif::[]
 endif::[]
 endif::[]
-ifdef::installer-foremanctl[]
+ifdef::foremanctl[]
 * If you use an external identity provider in your deployment, ensure the provider did not create the `{apache-user}` user account on the system.
 This user account can cause conflicts with the local users that {ProductName} creates.
 endif::[]

guides/doc-Installing_Server_foremanctl/master.adoc

@@ -4,7 +4,7 @@ include::common/header.adoc[]
 :context: {project-context}
 :mode: connected
 :ProductName: {ProjectServer}
-:installer-foremanctl:
+:foremanctl:
 
 = {InstallingServerCTLDocTitle}