support for moduleIf in context operations

[boutell]

Summary

Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"

What are the specific steps to test this change?

See corresponding doc-template-library PR

What kind of change does this PR introduce?

(Check at least one)

• Bug fix
• New feature
• Refactor
• Documentation
• Build-related changes
• Other

Make sure the PR fulfills these requirements:

• It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
• The changelog is updated
• Related documentation has been updated
• Related tests have been updated

If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

[linear]

PRO-4648 Making templates for images, image tags, files, and file tags does not make sense

The list of types you can pick from is long and contains things that are silly.

We need an easy, documented way to suppress this option on a per-type basis, via an option to that type's module, and we need to use "improve" to apply those to some standard types in the doc-template-library module.

PRO-4684 "Save As Template" offered for inappropriate types

Users, for instance.

[boutell]

Merge conflicts resolved. Same changes.