Prevent conflict between variable names in Resource.save! – this was cau...

This error was causing a nasty error a nasty error when we'd successfully saved a sublist, but on retrieving it would send the sublist data that it was going to push up in the fields column, instead of the array of sublist fields that we needed to.

This is because "sublists" should only be used to access that particular class' list of sublists and field names for each one.

To fix it, I just changed the name of the sublist data that we're pushing up to NS.

Extra detail added to resource_spec to test that we're sending the correct parameters to it.