Fix issue where prepared statement can only be used once

[mjmasn]

Move sqlite3_reset call after sqlite3_step in opsqlite_execute_prepared_statement

Fixes issue where new data does not correctly bind to a prepared statement after the first execution when inserting records, causing an unique constraint exception:

Error: Exception in HostFunction: [op-sqlite] SQLite code: 19 execution error: UNIQUE constraint failed: mytable.id

Can't share an exact reproduction but the general gist of the issue is doing something like this fails (id is a text primary key):

const statement = db.prepareStatement('INSERT INTO mytable (id, name) VALUES (?, ?)');

for (const record of records) {
  statement.bind([record.id, record.name]);
  statement.execute();
}

PS Happy to add some tests for this if it looks like a reasonable approach.

[ospfranco]

I wonder why CI is not working. Did you merge main from your fork?

[ospfranco]

This is weird, if a statement has finished executing with previous params, rebinding it should have the opposite effect of this PR. Please do add the tests, while I read up on reset.

There is already a test for rebinding the prepared statement and it is working correctly?

it('allows re-binding a prepared statement', async () => {
      const statement = db.prepareStatement('SELECT * FROM User WHERE id=?;');
      statement.bind([1]);

      let results = statement.execute();
      expect(results.rows!._array[0].name === 'Oscar');

      statement.bind([2]);
      results = statement.execute();
      expect(results.rows!._array[0].name === 'Pablo');
    });

[ospfranco]

Oh wow, nvm, it indeed fails. Weird!

[ospfranco]

Moving it down indeed fixes the issue, though I still do not understand why. Will merge it for now. Thanks for the PR!