Conform openapi schema names to not use existing typescript types #2163
Description
Related to front-end issue PhilanthropyDataCommons/front-end#1240
Currently, the 'file' schema in our openapi definitions clashes with the existing typescript 'file' type on sdk generation. The end result is that our 'file' gets built into a type named 'ModelFile', which is fine, but it also means that any type that references the schema 'file' does not actually resolve that reference (i.e bulkUploadTask in our typescript sdk types proposalDataFile as any). At a minimum we should think of a reasonable name for the schema in our api docs.