Rename gate bug when GatingStrategy has more than 1 gate with same name

[catcd]

Problem Description:
There is an issue in the rename_gate function at line 259, causing an inconsistency in the gate hierarchy when renaming a gate. The problem arises during the retrieval of successor gates after the initial renaming process.

Steps to Reproduce:

1. Start with the following gate hierarchy:

   root
   ├── CD4 mémoires
   │   ╰── A
   │       ├── A1
   │       ╰── A2
   ╰── CD4 naifs
       ╰── A
           ├── A1
           ╰── A2

2. Call the function: rename_gate('A', 'A new', ('root', 'CD4 naifs')).

Observed Behavior:

• The renaming process occurs prematurely between lines 247 and 254, changing the name A to A new.
• When attempting to retrieve the successor gate 'A1' in line 259 using the hierarchy ('root', 'CD4 naifs', 'A'), it fails because:
  • There are now two A1 gates in the hierarchy.
  • No gate matches the new name A new.

Potential Root Cause:

• The renaming logic alters the hierarchy prematurely (between lines 247 and 254) before successor gates are resolved. This leads to mismatched references when rename_gate attempts to access successor gates in line 259.

Suggested Fix:

• I have fix the problem by add this line before line 259:

s_tuple = tuple(s if s != gate_name else new_gate_name for s in s_tuple)

[catcd]

This bug does not happen if these is no A1, A2 in ('root', 'CD4 mémoires', 'A'), aka A1, A2 has only 1 note match