FormService.saveFormResouce doesn't effectively replace existing resources

If a user adds a form resource with a name 'x' and then later tries to replace it with a new value but same resource name 'x', it fails with an error message 'that the resource name is a duplicate entry for the form', which is technically true. However, the logic in FormResource.saveResource ineffectively attempts to replace it by first deleting the existing one which fails because the deleted object is still hanging around in the hibernate session.