feat: allow SymbolicCompilerPasses (SCP) passes during code generation

[DhairyaLGandhi]

Checklist

• Appropriate tests were added
• Any code changes were done in a way that does not break public API
• All documentation related to code changes were updated
• The new code follows the
  contributor guidelines, in particular the SciML Style Guide and
  COLPRAC.
• Any new documentation only uses public API

Additional context

Adds SymbolicCompilerPasses as a dep to allow passing optimization levels for array functions during symbolic code generation. The passes are an opt-in for now, and can be passed via the optimize kwarg to ODEProblem since JuliaSymbolics/Symbolics.jl#1755.

Add any other context about the problem here.

[DhairyaLGandhi]

The API can now work as:

resolve_optimize_option(0) == resolve_optimize_option(false) == resolve_optimize_option(:none) == nothing # no optimization
resolve_optimize_option(1) == resolve_optimize_option(true) == resolve_optimize_option(:basic) == SCP_BASIC
resolve_optimize_option(2) == resolve_optimize_option(:aggressive) == SCP_AGGRESSIVE

So users can pass

ODEProblem(...;
    optimize = 0/1/2,
              true/false,
              :basic/:aggressive/:none,
              MTK.SCP_BASIC/AGGRESSIVE/ vector of rules)

[DhairyaLGandhi]

Bump

[DhairyaLGandhi]

Bikeshedding: What should the keyword be called? Code gets optimized regardless based on Julia's optimization levels etc, so a more appropriate name might be array_optimizations