Consider standardizing default thread name prefixes for MVC async executors

Description:

I noticed that the default thread name prefix used by MVC async execution differs from other task infrastructure components.

Current MVC async executor:

public class RequestMappingHandlerAdapter extends AbstractHandlerMethodAdapter
		implements BeanFactoryAware, InitializingBean {

....
private class MvcSimpleAsyncTaskExecutor extends SimpleAsyncTaskExecutor {
....
      MvcSimpleAsyncTaskExecutor() {
          super("MvcAsync");
      }
....
}

produces thread names like:

MvcAsync1
MvcAsync2

while task scheduling infrastructure commonly uses prefixes such as:

task-1
task-2

using a hyphen separator and lower-case naming.

Is the current MvcAsync prefix intentional for historical or compatibility reasons?

I am not necessarily proposing a direct change because it would alter externally visible thread names and may impact logging or monitoring setups. I wanted to ask whether there has been discussion around standardizing naming conventions across Spring task-related infrastructure, perhaps for future major versions.

Thanks.

Start by reading RequestMappingHandlerAdapter and its MvcSimpleAsyncTaskExecutor, focusing on the current "MvcAsync" thread-name prefix. Compare it with the task infrastructure naming mentioned in the issue and investigate whether existing compatibility concerns affect standardization. Done means reaching a documented decision or a clearly scoped proposal for any future change.