Use specific error for exceptions raised by create_scalar_function

Typically APSW has more precise errors than Sqlite3, this is one of the exceptions.

When using `create_scalar_function` in `deterministic mode`, it is possible to throw an exception based on Sqlite constraints. In sqlite3 this raises a `sqlite.NotSupportedError`, but there is nothing specific in APSW. In fact, we're not sure what error is raised, so we lump it under `apsw.Error`. Some better things we can do:

1. Figure the specific error and capture/raise that as necessary
2. If there is no specific error, open a ticket, submit a PR to the upstream APSW library

> [!NOTE]
> This is documented as a comment in the `register_function` code within this library

Comienza leyendo el comentario en el código de register_function y reproduciendo una excepción de create_scalar_function en modo determinista. Compara la excepción con sqlite3.NotSupportedError e inspecciona cómo se capturan actualmente los errores de APSW. Se considera terminado cuando se genere un error específico de APSW, si está disponible, o cuando se documente y escale el error faltante a través del proyecto APSW upstream.

Escrito por el modelo de indexación a partir del texto del issue.