Async AASX File Server Profile

[sebbader-sap]

Closes #347

[CLAassistant]

All committers have signed the CLA.

[g1zzm0]

@Rudra-sandeep can you please sign the CLA

[g1zzm0]

Checked change of 3.1 version to 3.2 in semanticIds
Checked remaing files 3.1 to 3.2
Checked no 3.1 in 3.1 files
Checked no 3.2 in 3.2 files

[aaronzi]

1. Version bumps to 3.2 look good. Can confirm that nothing was missed.
2. The new async profile for the AASX File Server is consistent with SSP-01 of the AASX File Server and async Operation invokation.

I just wonder about two preexisting "problems":

• Why are description endpoints different when looking at the components? Some include more error responses than others
• Why is the handleId not explicitly mentioned in the 202 status so that clients know what to expect when calling those status endpoints?

[sebbader-sap]

Why is the handleId not explicitly mentioned in the 202 status so that clients know what to expect when calling those status endpoints?

@aaronzi That's a very valid point. I need to think about how we made this with the SME Operation invocations...

[sebbader-sap]

I remember it now: The 202 Accepted response has the Location response header, which can be used to provide the status URL, including the handleId part.