Remove context change in assembly

[Lennonka]

In #2492, we didn't realize that changing the context in assemblies will mess up the link anchors.
So this PR undoes that.

• I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• Foreman 3.8/Katello 4.10
• Foreman 3.7/Katello 4.9 (planned Satellite 6.14)
• Foreman 3.6/Katello 4.8
• Foreman 3.5/Katello 4.7 (Satellite 6.13)
• Foreman 3.4/Katello 4.6 (EL8 only)
• Foreman 3.3/Katello 4.5 on EL7 & EL8 (Satellite 6.12 on EL8 only; orcharhino 6.4/6.5 on EL8 only)
• Foreman 3.2/Katello 4.4 on EL7 & EL8
• Foreman 3.1/Katello 4.3 on EL7 & EL8 (Satellite 6.11 EL7/8; orcharhino 6.3 on EL7/8)
• We do not accept PRs for Foreman older than 3.1.

[github-actions]

The PR preview for db20338 could not be generated

[maximiliankolb]

I noticed those issues myself when building the docs which is why I changed the context in the assemblies. Does it help to reduce the number of affected modules? I am afraid we cannot keep the context as is because some files are included multiple times.

My ideal solution would be to have, for example, the "CRname" as part of the anchor/link to ensure there are no "id already assigned" warnings.

[Lennonka]

Actually, this problem came up with a modification in our downstream branding. The context in the links has been like this for a while (even before #2492), it seems that we forgot to update our UI links. Therefore, it isn't an issue and I'm closing this.