Degraded Performance loading scorm statics files

[johanseto]

Description

Hi, I was using this xblock in version 16. Then I updated to version 19.0.1 and I noticed the scorm was slower than usual.
We used to proxy the requests for the scorm assets directly to S3 but now it requires them to be served directly through the LMS. We were using directly S3 S3Boto3Storage passing the custom_domain kwarg.

Now, I found that in this commit ea54a52

This changes how the files pass each static are loaded through the Django-server.
The storage function URL was removed.
ea54a52#diff-e9b43e0a1aaf2777389c708425492661ab8f0e10b102afab1cd95acb07f8666aL429

I know that if was for security reasons for private buckets. But each static has to be processed by the LMS-server and the difference is appreciated loading a full scorm.

This is a comparison only for one static file.

V19.0.1

v18.0.2