Skip two randomly failing tests on SQLite

[waiting-for-dev]

Summary

db88911 set those two tests as pending because they were consistently failing. However, 5cdc40b removed the pending status because they started to work without problems.

Now it's not clear which situations affect them. When they fail, they do it consistently (for instance, they affected
#4379), but then sometimes they're ok. Until we have a better understanding, we'll just skip them, as they only affect the SQLite adapter.

Checklist

Check out our PR guidelines for more details.

The following are mandatory for all PRs:

• I have written a thorough PR description.
• I have kept my commits small and atomic.
• I have used clear, explanatory commit messages.

The following are not always needed:

• 📖 I have updated the README to account for my changes.
• 📑 I have documented new code with YARD.
• 🛣️ I have opened a PR to update the guides.
• ✅ I have added automated tests to cover my changes.
• 📸 I have attached screenshots to demo visual changes.

[elia]

It looks like they're again an issue, and #4379 is being affected.

You think we're dealing with a flakey or is it a hard stop for sqlite?
If it's a specific behavior I'm also wondering if we could add a reference to what is causing it in the pending message 🤔

[waiting-for-dev]

You think we're dealing with a flakey or is it a hard stop for sqlite?
If it's a specific behavior I'm also wondering if we could add a reference to what is causing it in the pending message

It doesn't look flaky, as it fails consistently.

👍 I added the same we have for the first commit message as the pending failure. My understanding of the failure is not complete, so I can't be more precise.