Support for Reconfiguration without Recreation of Service Pod?

## What is changing? (Please include as many details as possible.)
Currently, when a Knative user changes the configuration of a Knative service in YAML, the Knative system will create a new revision of it and require the service pod to be recreated. But in fact, for some service configuration changes, there is no need to recreate the pod. For example, changes to the "containerConcurrency" of a Knative service can be implemented without recreating its pods. Also, some configuration changes about Knative Autoscaler do not require pod re-creation, since this configuration change has nothing to do with Kubernetes pods.

## How will this impact our users?
It would be a good thing if reconfiguration without pod re-creation is supported, in some cases Knative users change the service configuration, which may reduce the chance of pod re-creation.

## In what release will this take happen (to the best of your knowledge)?
Ex. v0.2-v0.3

## Context
Link to associated PRs or issues from other repos here.
In-place reconfiguration requests for kubernetes VPA:
[https://github.com/kubernetes/kubernetes/pull/102884#discussion_r1019704157](url)

## Additional info
No

No source file, test, or entry point is named. Start by reviewing the requested in-place reconfiguration behavior and the linked Kubernetes VPA discussion; done would identify which Knative service and autoscaler changes can be applied without recreating service pods.

Written by the indexing model from the issue text.