v4.1.0

• [Breaking] Removing support for Bearer scheme and adding FunctionsBearer

  Recent security updates in the Azure Functions runtime are clashing with the use of the default, well known Bearer scheme.
  
  One of the effects of this change is the portal not able to interact with the functions app to retrieve runtime information and in some cases not able to retrieve functions information.
  In the past this was not an issue and application was able to replace the default Bearer configuration to enable the functionality provided by this package.
  
  Starting from this version, using the default AddJwtBearer with no custom name, will produce an error. You will have 2 options: you can switch your app to use AddJwtFunctionsBearer method without providing any name which will map your configuration to the FunctionsBearer scheme, or you can use AddJwtBearer("<your-custom-scheme>", ...) to specify something different.