feat: making span processor type configurable

[varkey98]

Description

Context is that aws lambdas generally can't use batchspanprocessor since there's a runtime freeze after the execution. We can use simplespanprocessor in that case so that span exportation is inline. In node/python lambdas we use tracerprovider.flush, but in case of aspnetcore lambdas we dont need a separate handler. We can use the existing automatic instrumentation, but would require a config option for the span processor.

Testing

Please describe the tests that you ran to verify your changes. Please summarize what did you test and what needs to be tested e.g. deployed and tested helm chart locally.

Checklist:

• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Any dependent changes have been merged and published in downstream modules

Documentation

Make sure that you have documented corresponding changes in this repository or hypertrace docs repo if required.

[tim-mwangi]

@varkey98 did you run make generate-proto generate-env-vars? I do not see changes to ENV_VARS.md

[varkey98]

@varkey98 did you run make generate-proto generate-env-vars? I do not see changes to ENV_VARS.md

I ran it. I don't think we generate env vars for enums. It's not there for other enums as well. But pls hold on reviews, thinking of closing this pr after discussing with @prodion23

[varkey98]

closing this pr