In-memory queue name are not scoped with pipelines

[laysakura]

Describe the bug

When a process creates 2 pipelines that include the same queue names, a panic occurs.

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior:

[2022-06-29T07:55:22Z ERROR panic] thread 'test_source_row_from_builder' panicked at 'called `Result::unwrap()` on an `Err` value: Sql(queue (q_sink_1) already exists)': springql/tests/test_support/
mod.rs:14
       0: backtrace::backtrace::libunwind::trace
                 at /Users/sho.nakatani/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.64/src/backtrace/libunwind.rs:93:5
          backtrace::backtrace::trace_unsynchronized
                 at /Users/sho.nakatani/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.64/src/backtrace/mod.rs:66:5
       1: backtrace::backtrace::trace
                 at /Users/sho.nakatani/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.64/src/backtrace/mod.rs:53:14
       2: backtrace::capture::Backtrace::create
                 at /Users/sho.nakatani/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.64/src/capture.rs:176:9
       3: backtrace::capture::Backtrace::new
                 at /Users/sho.nakatani/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.64/src/capture.rs:140:22
       4: log_panics::init::{{closure}}
                 at /Users/sho.nakatani/.cargo/registry/src/github.com-1ecc6299db9ec823/log-panics-2.0.0/src/lib.rs:52:25
       5: std::panicking::rust_panic_with_hook
                 at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:702:17
       6: std::panicking::begin_panic_handler::{{closure}}
                 at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:588:13
       7: std::sys_common::backtrace::__rust_end_short_backtrace
                 at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:138:18
       8: rust_begin_unwind
                 at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:584:5
       9: core::panicking::panic_fmt
                 at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:143:14
      10: core::result::unwrap_failed
                 at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/result.rs:1749:5
      11: core::result::Result<T,E>::unwrap
                 at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/result.rs:1065:23
      12: feat_source_row::test_support::apply_ddls
                 at tests/test_support/mod.rs:14:9
      13: feat_source_row::pipeline
                 at tests/feat_source_row.rs:54:5
      14: feat_source_row::test_source_row_from_builder
                 at tests/feat_source_row.rs:88:20

1. git checkout e335b74895b67d60591e3b44e4e75c0aac83b246
2. cargo test -p springql --test feat_source_row

Expected behavior

Both the two tests succeed.

Environment

GitHub Actions