[BEAM-4028] Step / Operation naming should rely on a NameContext class

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: Not applicable
• Component/s: sdk-py-core
• Assignee: Pablo Estrada
• Reporter: Pablo Estrada
• Created: 06/Apr/18 18:02
• Updated: 17/Oct/21 00:52
• Resolved: 30/Apr/19 17:37

Description

Steps can have different names depending on the runner (stage, step, user, system name...). 

Depending on the needs of different components (operations, logging, metrics, statesampling) these step names are passed around without a specific order.

Instead, SDK should rely on `NameContext` objects that carry all the naming information for a single step.

Issue Links

• links to: GitHub Pull Request #5043
• links to: GitHub Pull Request #5135
• links to: GitHub Pull Request #6123
• links to: GitHub Pull Request #15652