=============================================================

At time of writing, the
[documentation for the NodeJS tracing library](https://docs.datadoghq.com/database_monitoring/connect_dbm_and_apm/?tab=nodejs)
on the DataDog website states that to switch off DBM Propagation in the tracing of
database calls, the mode should be set to the value `none`.

This, however, leads to terminal hanging in the use of the mysql/mysql2 Node modules.

In debugging this, I determined that the documented value of `none` is no longer valid
and the value `disabled` should be used instead. While this is clearly a documentation
inconsistency, the fact that the plugin does not handle an unexpected value for `mode`
leads to a break in functionality when `dd-trace` is upgraded from version `1.7`, when
this value presumably changed.

This bug is caused by the unrecognized value - in this case `none` - falling through the
database plugin's `injectDbmQuery` function without returning a query.

Therefore, this commit accommodatesthe old/documented value of `none` that disables
propagation as well as defaults the behavior of the function to return the query
unmolested in the event that an invalid value is used in future.

I could not see any unit tests for this, but this has been tested "in the wild" to success
within my own test setups, and should be easily backported to previous versions.

I also suggest that the documentation linked above is updated to reflect the "proper"
value.

…hould not be functionally different, and should let the SQL through

)

* Avoid run sequelize plugin test with non compatible mysql2

* Avoid run sequelize plugin test with non compatible mysql2

* Fix typo

* Fix typo

* Add comment with the test combination constraint explanation

* Update packages/dd-trace/test/appsec/iast/analyzers/sql-injection-analyzer.sequelize.plugin.spec.js

Co-authored-by: simon-id <simon.id@datadoghq.com>

---------

Co-authored-by: simon-id <simon.id@datadoghq.com>

* Emit an event when profiles are submitted
* Emit span start event
* Emit an app-closing event so telemetry users can publish final metrics
* SSI Telemetry class
* Telemetry mock profiler

Because commas are normalized to underscores in backend anyway.

… in Cypress (DataDog#4228)