Scc 4549/phys override spec

[charmingduchess]

https://newyorkpubliclibrary.atlassian.net/browse/SCC-4549

• refactor physRequestable function to be extremely explicit about what determines physical requestability
• removes finding aid from spec requestability criteria
• removes specRequestable overriding physRequestable. Looking closer at our nypl-core data, I'm pretty sure this is not necessary at all. All but two special collections locations are actually listed as requestable: false. I do think these locations should be updated to false, but it doesn't affect this work, because they don't have any deliverableTo locations anyway. Similarly, I believe we should leave all the deliverableTo locations, but it doesn't actually impact this work.
• update one fixture with extant customer code

This update should be QA'd pretty closely, looking at examples that:

• have deliverableTo and special collections locations
• have requestable:false, no delivery locations, and special collections access type
• are partner records mentioned in the ticket

[nonword]

Seems much cleaner to me!