hotfix: site curator only relevant for curateable path/method

[daisieh]

I noticed a failure in the integration tests: I need to separate the readable path/method combos from the curateable ones, and site curators are only allowed to curate curateable ones, regardless of program. This is how we can allow site curator to create non-existent programs without allowing them to read programs they're not authorized for. (Is this actually the behavior we want?)

[mshadbolt]

I think given a site_curator can modify program authorizations, it wouldn't make sense for them to not be able to ingest/delete programs that they didn't specifically create. Therefore I think it makes sense for site curators to be able to read/ingest/delete any program at a site.

For testing purposes, I don't think the test users should be given any default site or program roles (apart from the need to set up a site admin). This will allow us to properly test the apis for setting up the roles during the tests, instead of having defaults and we assume the functionality is in place.

[kcranston]

Agree that site curators should be able to read / write all programs. Thanks for the change.