Improve stack overflow, show more properties in Error objects

[Jarred-Sumner]

What does this PR do?

I got sidetracked while trying to make the postgres client throw better errors

Fixes #817
Fixes #185

In order to be able to display all the own properties of Error objects when you console.log them, we need to handle stack overflow

In order to handle stack overflow, we need a way to track stack overflow

Now that we have a way to know in Zig if there's a stack overflow, I added it to the JS parser so we can handle stack overflow while visiting

Also, we should not be using std.bit_set. It copies the entire 90 KB bitset onto the stack. Our bun.bit_set fixes that.

How did you verify your code works?

There are some tests.

[robobun]

^{Updated 11:07 PM PT - Dec 25th, 2024}

✅ @paperdave, your commit 1cf8c16 has passed in #8527! 🎉

---

🧪   try this PR locally:

bunx bun-pr 15985

[kravetsone]

Great! I want to report it soon but u already open this))

This happened with my TelegramError extended from Error class

I add additional keys such as params as a better way to determine which parameters are used in this failed request

But it shows only in Node for now(