Argo stacks file access can be inhibited by rightsMetadata access rules

[LynnMcRae]

Example: https://argo.stanford.edu/catalog/druid:jd779cx9795 has a jp2 file in the stacks. Argo just offers a stacks URL to get you the file, which it (properly) blocks the download because of the no-download rule in rightsMetadata.

Argo file access should be independent of rightsMetadata and those its rules. This may be a dor-rights-auth change, but we would need to figure out how stacks could know that the request originates from Argo. This may not be possible if it is a link direct from the user's browser, requiring Argo to proxy the file request or use an alternate access path to the stacks directories.