Etherlink/Node/Tx_queue: propagate the Name module

This MR is stacked on !18322 (merged).

What, why, and how

This MR is needed to avoid registration conflict when the Tx_container module will be instantiated several times (once for Etherlink and once for Tezlink).

Each instantiation of the Tx_container functor leads to the registration of the tx_queue_is_closed error and some events. They need to have a different id each time they are registered, which we can achieve by using different Name modules (and in particular different Name.base lists).

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR