Description of problem:
Having Satellite or (mainly) Capsule with default tuning profile, /etc/httpd/conf.modules.d/event.conf is configured with

MaxClients 150

That leads to raising a warning during httpd start:

Oct 16 09:18:49 pmoravec-caps612.gsslab.brq2.redhat.com httpd[1076]: AH00513: WARNING: MaxRequestWorkers of 150 is not an integer multiple of ThreadsPerChild of 16, decreasing to nearest multiple 144, for a maximum of 9 servers.

which can raise alarms at or confuse customers.

Any tuning profile starting from medium does bump this value to 1024:

/usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/extra-extra-large.yaml:apache::mod::event::maxrequestworkers: 1024
/usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/extra-large.yaml:apache::mod::event::maxrequestworkers: 1024
/usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/large.yaml:apache::mod::event::maxrequestworkers: 1024
/usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/medium.yaml:apache::mod::event::maxrequestworkers: 1024

but the default keeps undefined:

/usr/share/foreman-installer/modules/apache/manifests/mod/event.pp: Optional[Variant[Integer, Boolean]] $maxrequestworkers = undef,

causing the default 150 is not overwritten.

Please adjust also the default profile to use something dividable by 16.

Version-Release number of selected component (if applicable):
Sat&Caps 6.12+ (probably also older)

How reproducible:
100%

Steps to Reproduce:
1. Install a Caps or Sat without tuning profile
2. journalctl --unit httpd.service -a --no-pager

Actual results:
2. shows the WARNING above

Expected results:
2. no such warning

Additional info:
The default 150 value is harmless, just the warning can cause confusion.