Forked from #40072.

While #64646 mitigates most of the performance issues related to creating single-use JsonSerializerOptions instances, this is still a suboptimal pattern and users are better off working with singleton JsonSerializerOptions instances. We should add an analyzer that warns about any JsonSerializerOptions construction that flows only to a call to a JsonSerializer method argument.

The analyzer should warn if any of the following patterns are detected:

JsonSerializer.Serialize(value, new JsonSerializerOptions { /* some custom config */ });

or if we're passing a local that has been initialized in the same method

var options = useDefault ? JsonSerializerOptions.Default : new JsonSerializerOptions { /* some custom config */ };

foreach(object value in values)
{
    JsonSerializer.Serialize(value, options);
}

In both cases the analyzer should recommend lifting the options instance to a static variable or use DI, but would most likely not provide a fixer.