Azure HTTP Functions compliant with TCK

[timyates]

This PR switches the Azure function handlers to use servlet-core in much the same way as the AWS module does.

Spotted working on this that in a previous PR #398 we broke the test code that we generate in Micronaut Starter (see #509 (comment))

I changed the tests in this module here https://github.com/micronaut-projects/micronaut-azure/pull/509/files#diff-5477701f4559e28df2025cfa073a4ca34eb84685ed452c0567f5c677f040a602

But I am not sure if it's correct...

I have tested this running a test project on Azure, and I think it's right, but it could do with someone who is used to using Azure to check we haven't broken anything important here

I also pulled in the context-path fix from #493 so we don't miss it (or someone else doesn't have to struggle with the merging)

Looking into DefaultExecutionContext to see why using it fails tests in third party apps

[timyates]

Right, this doesn't work as starter generates code such as:

        HttpRequestMessageBuilder.AzureHttpResponseMessage response =
            function.request(HttpMethod.GET, "/demo")
                    .invoke()

This was broken by #398

[timyates]

Tried it in real azure

Returns no content 😭

[timyates]

So I think it's an issue with getNativeResponse 🤔

[timyates]

Raised micronaut-projects/micronaut-starter#1890 to deal with starter generating test code that doesn't work with 4.0.0

[wetted]

Looks like a real nice piece of work. Congrats on clearing all the TCK tests.

[sdelamo]

We need to document you can bind:

com.microsoft.azure.functions.ExecutionContext
com.microsoft.azure.functions.HttpRequestMessage
com.microsoft.azure.functions.TraceContext

[sdelamo]

It misses documentation about change.

[sdelamo]

I think we should move this class to io.micronaut.netty.cookies in core.

[sdelamo]

@timyates create an issue for this and add it to 5.1.0 Release project.

[sdelamo]

@graemerocher can you review this PR? It currently passes every TCK test and I have changed it to tell users they have to remove the azure api route prefix and then they can use normally micronaut.server.context-path if they wish for a prefix.

[sdelamo]

We need to document you can bind:

com.microsoft.azure.functions.ExecutionContext com.microsoft.azure.functions.HttpRequestMessage com.microsoft.azure.functions.TraceContext

I have created an issue for this.

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
1.4% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint