fix: increase timeout for BatchSpanProcessor test

[mayurkale22]

Which problem is this PR solving?

• Resolves BatchSpanProcessor test failing intermittently #350.

• Increasing timeout number, this should give enough time to report spans collected by BatchSpanProcessor.

[codecov-io]

Codecov Report

Merging #382 into master will increase coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #382      +/-   ##
==========================================
+ Coverage   97.94%   98.07%   +0.13%     
==========================================
  Files         106       46      -60     
  Lines        5103     1144    -3959     
  Branches      431       88     -343     
==========================================
- Hits         4998     1122    -3876     
+ Misses        105       22      -83

Impacted Files	Coverage Δ
packages/opentelemetry-core/src/common/time.ts	92.68% <0%> (-3.93%)	⬇️
...ckages/opentelemetry-core/src/common/NoopLogger.ts	40% <0%> (-2.86%)	⬇️
...core/src/context/propagation/BinaryTraceContext.ts	96.15% <0%> (-2.21%)	⬇️
...telemetry-core/src/context/propagation/B3Format.ts	94.59% <0%> (-1.33%)	⬇️
...s/opentelemetry-core/test/context/B3Format.test.ts	100% <0%> (ø)	⬆️
...s/opentelemetry-core/test/trace/tracestate.test.ts	100% <0%> (ø)	⬆️
...entelemetry-core/test/common/ConsoleLogger.test.ts	100% <0%> (ø)	⬆️
...ckages/opentelemetry-core/test/common/time.test.ts	100% <0%> (ø)	⬆️
.../opentelemetry-core/src/trace/spancontext-utils.ts	100% <0%> (ø)	⬆️
...s/opentelemetry-core/test/trace/NoopTracer.test.ts	100% <0%> (ø)	⬆️
... and 73 more