Make Node and ExprTransform affect OpPropFunc arguments

[Aklakan]

As the title says. (If desired I can create an issue). The issue occurred to me when I was trying to post process variable names in Ops after the optimizer had already run. OpPropFunc arguments were not affected then.
One detail question is whether the NodeTransform should affect the property function URI.
My argument against it are:

• It's probably desired to prevent a node transform from mapping a property function name to a blank node or literal.
• Renaming property function names in the BGPs could be done before the optimizer runs.
• In the work case, it would still possible to subclass TransformCopy just for that case.

---

• Tests are included.
• Commits have been squashed to remove intermediate development commit messages.
• (Key commit messages start with the issue number (GH-xxxx))

By submitting this pull request, I acknowledge that I am making a contribution to the Apache Software Foundation under the terms and conditions of the Contributor's Agreement.

---

See the Apache Jena "Contributing" guide.