Changing resource from restricted to public is not picked up by xloader

[brooks-eco]

ckan 2.11

Steps to reproduce

1. Create dataset - public access
2. Create resource with a "restricted access" token (via this extension)
3. Note that XLoader will not load to DataStore because of the restricted permission.
4. Edit the resource restricted_api auth field back to "public"
5. SAVE resource
6. edit resource - load to Data Store
7. ERROR: XLoader will not load to DataStore because of the restricted permission. (despite having changed to public). This seems like a bug - we just set the auth back to public yet xloader is still stuck.

The workaround is.

8. delete the resource
9. recreate and this time ensure restricted_api field is set to "public" on creation
10. load data to the data store
11. now can edit the resource and switch to "restricted setting" and all is good - data views and API available to logged in users only.

It would be more elegant if xloader inherited the change in auth from restricted when created with subsequent change to public .