…ing for interactive tools

Replace the class `InteractiveToolSqlite` in lib/galaxy/managers/interactivetool.py with a new class `InteractiveToolPropagatorSQLAlchemy`. The new class implements a SQLAlchemy "propagator" for `InteractiveToolManager` (on the same file). This propagator writes the mappings to the table named after the value of `DATABASE_TABLE_NAME`, in the database specified by the SQLAlchemy database url passed to its constructor. Change the constructor of `InteractiveToolManager` so that it uses `InteractiveToolPropagatorSQLAlchemy`.

Change the method `_process_config` of `galaxy.config.GalaxyAppConfiguration` so that it converts the value of `interactivetools_map` to a SQLAlchemy database url if it is a path.

Update documentation to reflect these changes.

…database url

…map_sqlalchemy` setting

Define a new configuration property `interactivetools_map_sqlalchemy` to store interactivetool proxy mappings on a RDBMS supported by SQLAlchemy.

If set, it takes precedence over `interactivetools_map`. When unset, a SQLite mapping file located at `interactivetools_map` is used (as usual).

…mple

This text is managed by Gravity

…ase_connection` or `install_database_connection`

…ools_map_sqlalchemy` setting

Refer to SQLite docs page describing situations where a client/server RDBMS works better and provide an example. Link to the `interactivetools_map_sqlalchemy` on the Galaxy configuration page.

```
lib/galaxy/managers/interactivetool.py:65: error: No overload variant of
"select" matches argument type "ReadOnlyColumnCollection[str, Column[Any]]"
```

…e first time

`lib.galaxy.config.GalaxyAppConfiguration._process_config` requires `sqlalchemy.engine.make_url` to forbid `interactivetools_map_sqlalchemy` from matching `database_connection` or `install_database_connection` (678bea1)

…etools_map_sqlalchemy` matches `database_connection` or `install_database_connection` (678bea1)

…chemy` is defined

Given that `interactivetools_map` is ignored if `interactivetools_map_sqlalchemy` is set, first check `interactivetools_map_sqlalchemy`. If it's not set, then build the sqlite url; but if it is set, then set `interactivetools_map` to `None` for clarity (and to avoid potential bugs in the future)

Co-authored-by: John Davis <jdavcs@gmail.com>

…ools_map_sqlalchemy`

Authored-by: John Davis <jdavcs@gmail.com>

…tools_map` in the latter's description

Co-authored-by: John Davis <jdavcs@gmail.com>

…sert()` or `delete()`

…tem__`

Match @jdavcs' coding style.

…emy.get()`

Emit a warning when `get()` returns no results.

…checks

…connection` and `install_database_connection`

Using `urlparse` rather than `sqlalchemy.engine.make_url` decreases the precision of the comparison, but removes the need to declare `sqlalchemy` as a dependency of the config package.

This is a tradeoff between convenience (preventing mistakes from the user) and complexity (number of dependencies of the config package).

This reverts commit b6ad695.