Revert modification to label of parent context in router

[leonlnj]

Description

This reverts the PR which was initially targeted to fix the label of traffic rules

For detailed explanation, refer to Turing PR which revert fiber from 2.1-rc1 to 2.0

Fundamentally, this behaviour occur due to eager and lazy router calling routes with different sequence.

• eager router call route with parent context, then call strategy
• lazy router call strategy, then call route with strategy context

Hence this PR reverts Fiber 2.1-rc1, until a solution fixes both metrics.

[krithika369]

@leonlnj, in the linked Turing PR, the original bug is with Selective Routing strategy + Default traffic rule, correct?

Calls all routes with context passed (contain NO traffic label, as it is pass the label from DefaultTuringRoutingStrategy which logs metric incorrectly)

[leonlnj]

Selective Routing strategy + Default traffic rule

Selective Routing strategy, yes. Its not default traffic rule, regardless of rule, at the lowest level it will call individual route with DefaultTuringRoutingStrategy

[krithika369]

Selective Routing strategy + Default traffic rule

Selective Routing strategy, yes. Its not default traffic rule, regardless of rule, at the lowest level it will call individual route with DefaultTuringRoutingStrategy

I see.. Got it. Will append this to the internal bug, can try to pick it up over the coming sprints. Thanks.