Correct Smart Proxy upgrade instructions on foreman-el

[ekohl]

What changes are you introducing?

On foreman-el there is no PostgreSQL present so there is no DNF module switching.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Eventually users should be able to follow the upgrade guide and actually get an upgraded system.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Note there are no upgrade instructions for EL9 and the setting up repository step for foreman-deb is completely missing.

It's also interesting that it upgrades the OS packages first and then the Foreman packages. That feels redundant to me.

@evgeni any thoughts on recommending foreman-maintain like we do in Satellite? That would help abstract away many of the differences and align on process.

Checklists

• [x] I am okay with my commits getting squashed when you merge this PR.
• [x] I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• [ ] Foreman 3.11/Katello 4.13
• [ ] Foreman 3.10/Katello 4.12
• [ ] Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
• [ ] Foreman 3.8/Katello 4.10
• [ ] Foreman 3.7/Katello 4.9 (Satellite 6.14)
• [ ] Foreman 3.6/Katello 4.8
• [ ] Foreman 3.5/Katello 4.7 (Satellite 6.13; orcharhino 6.6/6.7)
• We do not accept PRs for Foreman older than 3.5.

[github-actions[bot]]

The PR preview for 74a8ed51951e354fe1d5439f52921f854bc0bb91 is available at theforeman-foreman-documentation-preview-pr-3223.surge.sh

The following output files are affected by this PR:

• Upgrading_Project/index-foreman-el.html

show diff

show diff as HTML

[evgeni]

Well, that's sadly not correct. You need the foreman module for foreman-proxy.rpm, and that pulls the PostgreSQL Module, so you gotta switch.

I had to when upgrading puppet01.

[ekohl]

Ah, you're right. I'm so glad we'll drop modularity soon when we drop EL8 in 3.13