Incorporate latest API changes in code examples #223
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
With Windows App SDK 1.8-experimental1 some APIs have changed that are not in the docs yet:
PackageDeploymentStatusenum does not exist anymore. Instead, theAIFeatureReadyResultStateenum is used.ExtendedError()is not a method anymore, but a property insteadGenerateResponseAsyncreturns aLanguageModelResponseResultand no more aLanguageModelResponseobjectLanguageModelResponseResultdoes not have the response in aResponseproperty, but in aTextpropertyGenerateResponseWithProgressAsyncdoes not exist anymore, it's now justGenerateResponseAsyncvar resultdeclaration inside an if-statement and avar resultdeclaration outside of the if-statement, which causes the code to not compile due to CS0136 error (A local or parameter named 'result' cannot be declared in this scope because that name is used in an enclosing local scope to define a local or parameter). I call the variable for the responseresponseinstead of result to avoid this.This PR fixes these things in the code examples to make them valid for Windows App SDK 1.8-experimental1.