I am also facing some issue with the "file arrival" trigger on one of my environments.
Its strange that it kept running fine until today where it broke. 
I always only had the "Storage Blob Data Contributor" for my Managed Identity ( Access Connector) and never had the other ones mentioned above? 
Could you please suggest on why would this work well until now?

I do not see any queues or event subscription being created for my envionments where this passed.

"""
An error occurred while processing file events in the external location associated with '/path/to/Volume': INVALID_STATE: Failed to list objects. There are problems on the location that need to be resolved. Details: Failed to provision file events resources during queue.create operation. Please ensure the IAM roles Storage Account Contributor, Storage Blob Data Contributor, EventGrid EventSubscription Contributor, Storage Queue Data Contributor are correctly assigned to your managed identity (or service principal, if used). Original error from the cloud provider: If you are using a StorageSharedKeyCredential, and the server returned an error message that says 'Signature did not match', you can compare the string to sign with the one generated by the SDK. To log the string to sign, pass in the context key value pair 'Azure-Storage-Log-String-To-Sign': true to the appropriate method call. If you are using a SAS token, and the server returned an error message that says 'Signature did not match', you can compare the string to sign with the one generated by the SDK.

"""