perf(bytecode): elide arguments object instructions when its never used

[DonIsaac]

What This PR Does

• Makes oxc's semantic analysis information available when compiling scripts
• Use that info to not generate instructions that create a function's arguments object when that function's body never references it

[aapoalas]

issue: I don't think you can take the Semantic out: a single source code can contain X amount of functions, and they compile separately.

[aapoalas]

As mentioned, the semantics should remain usable multiple times over.

Otherwise, this is a great addition that will definitely be helpful in the future! Us not taking advantage of the semantic analysis oxc performs is a big mistake :)

[aapoalas]

I did a refactoring pass on this because I wanted to merge this but found a couple of issues with using the Semantic's unresolved functions.

First, just checking the body isn't enough: we need to also check the formal parameters, but that was easy to solve.

A problem that is not easy to solve is that we don't get "arguments" as unresolved here:

var arguments = undefined;
function foo() {
  return arguments.length;
}

So the check says that the foo function doesn't need the arguments object, but it does.

Another issue is that in this function we again get the wrong result from the check:

function __func(){
    return typeof arguments;
    var arguments = "foo";
};

arguments is not unresolved, so the object doesn't get created.

A third issue is that eval can also mess with arguments, and of course this check doesn't guard for eval. So, that also needs checking.

It honestly seems like it'd be easier to not use the Semantic object at all, and instead just walk the AST and check references in it manually. That would also mean that Program could be handled like previously. Right now I had to move it into the SourceCode because Semantic holds a reference to Program.