Fixes (includes issue number if applicable):

• Allows the user to type any string as a key in the resource config object—not just a resourceKey—and have the return from useResources typed correctly.
• Previously this functionality worked in the library but the user would need to apply a few @ts-ignores because TypeScript wouldn't recognize it.

ie, this will work now:

getResources = () => ({
  myResource: {resourceKey: "user"}
});


// ...
const {myResourceModel} = useResources(getResources, {}); // myResourceModel is type userModel