Clean up response compression about basicmiddleware

[Yves57]

Maybe adding "image/svg+xml" to the default types.

[muratg]

Putting in 1.1.0 for now. We can move it to 1.2.0 if we can't finish this off in time.

[Tratcher]

GZipStream allocations: https://github.com/dotnet/corefx/issues/12549

[muratg]

@Tratcher Per PM decision, version numbers for new packages will be 1.0.0-preview1 for the initial release. (Not 1.1.0-preview1)

[Tratcher]

Review feedback:

• Should the services be registered as singleton or transient? Eilon said Singleton.
• Split ResponseCompressionExtensions by services vs appbuilder.
• Rename EnableHttps to EnableForHttps
• Try binding Options from Config
• Configurable services should resolve their own options rather than being instantiated, configured, and registered as instances.
• See how MVC adds filters, something about adding the type to am list on options and then creating the type from DI.
• Remove the AddResponseCompression(params string[]) overload, investigate defaults and wildcards instead. Text/*, Application/javascript. #121

[Tratcher]

Reading from config works pretty well:

{
  "section": {
    "EnableForHttps": true,
    "MimeTypes": ["text/plain", "text/html"]
  }
}

            services.AddResponseCompression(options =>
            {
                Configuration.GetSection("section").Bind(options);
            });

[Tratcher]

Possible default mime types (things used by the template, static files):
text/css
text/html
application/javascript

WebApi:
application/xml
text/xml
application/json
text/json
application/json-patch+json

Other:
text/plain

[Tratcher]

@Yves57 justification? We're not trying to capture every possible type, just the ones to make the 90% scenario work. I based this list on the files included in the full WebApp template, as well as those types from MVC/WebAPI.

[Tratcher]

Closing this now that we've worked through the main checklists. Further questions, feedback, etc. should be filed in new issues.

[Yves57]

@Tratcher Because SVG is a standard included in W3C recommandations. So I don't think it's "exotic"...