fix(sqlite): query macro argument lifetime use inconsistent with other db platforms

[iamjpotts]

Demonstrates but does not fix Fixes an inconsistency with allowed usage of references as arguments to query macros in the context of the sqlite feature compared to features for other db platforms, such as Postgres.

Compare the test added with this pr vs the existing test by the same name for Postgres:

The existing test for Postgres compiles and passes because PgArguments does not have a lifetime parameter. The new test for sqlite fails would fail to compile because SqliteArguments has had a lifetime parameter which causes the return value of the query! macro to be borrowing a reference to a value that is an argument to query! but goes out of scope when query! returns.

Does your PR solve an issue?

No (not yet)
Yes - cannot pass a reference as a bind argument to query! unless the reference is established before the query! macro call (e.g. by assigning it to a variable with let).

Is this a breaking change?

Likely yes. A fix would likely involve adding or removing lifetime parameters on structs related to arguments, and those structs are a part of the crate's public api.

Yes, due to:

• Deletion of lifetime parameter on SqliteArguments and SqliteArgumentValue
• Deletion of into_static() on both of those types
• Introduction of SqliteArgumentsBuffer type to wrap Vec<SqliteArgumentValue>
• Changing SqliteArgumentValue::Text to store an Arc<String> instead of Cow<str>, and adding ::TextSlice for the Arc<str> variant

Commits

The first commit is a part of #3956.

The last commit (changing AnyArguments::convert_to to convert_into) could be moved out of this pr and into a new one focused on removing the lifetime arguments on AnyArguments and AnyArgumentValue to add similar support for references in the bind parameters when using the Any driver.