[V2] Missing security schemes when inlining references are enabled to write a document.

[andrueastman]

One of the effects of enabling InlineLocalReferences and InlineExternalReferences in this PR is that the library will attempt to resolve the references and not write the components section.
https://github.com/microsoft/kiota/blob/e4b45e9f12c0fa1daea76f1849618ee953e73e49/src/Kiota.Builder/Plugins/PluginsGenerationService.cs#L64

See reference in library at

OpenAPI.NET/src/Microsoft.OpenApi/Models/OpenApiComponents.cs

Line 111 in 0a12b63

if (writer.GetSettings().InlineLocalReferences)

The OpenApi.Net library should probably inline the Security Requirement Object in the operation level for the scenario when inlining references or have the components section always write the securitySchemes in the components sections if this is an exception.

Related to microsoft/kiota#6279

[darrelmiller]

@andrueastman It is not allowed to inline security schemes into security requirement objects. When doing local inlining we should not remove the #/components/securitySchemes section in the output document.