Span activation should activate parent context

Is your feature request related to a problem? Please describe.

Baggage propagation is not intuitive.

Describe the solution you'd like

I would like to be able to access the baggage, even if I omit the extractedContext.makeCurrent() statement below:

        Context extractedContext = textMapPropagator.extract(Context.current(), req, EXTRACT_PROPERTIES_FROM_HEADER);
        try (Scope ignore = extractedContext.makeCurrent()) {
            Span serverSpan = tracer.spanBuilder(handlerMethodName(req, handlerMethodPerInfo))
                                    .setParent(extractedContext)
                                    .setSpanKind(SERVER)
                                    .startSpan();

            try (final Scope scope = serverSpan.makeCurrent()) {
               //here I have access to baggage using Baggage.current()
            } finally {
                serverSpan.end();
            }
        }

Describe the solution you'd like

I already passed extractedContext to the span and activated it.

Start by reproducing the Context.extract(...), makeCurrent(), SpanBuilder.setParent(...), and Baggage.current() sequence shown in the issue, then inspect the SDK's context and span-activation entry points. Determine and test the intended parent-context behavior; done means the requested baggage access works without the separate extractedContext.makeCurrent() scope, with lifecycle behavior covered by tests.