correct the customApiIntercept loading case

`req.reply()` was not returning an empty response, it was returning the
actual response from the server. this led to the "loading" state being
present momentarily before the actual response was returned. we are now
forcing the loading state to remain, as the mock intends.

Author: alishaevn

cypress/support/commands.js

@@ -23,6 +23,7 @@
 //
 // -- This will overwrite an existing command --
 // Cypress.Commands.overwrite('visit', (originalFn, url, options) => { ... })
+
 import { scientistApiBaseURL } from './e2e'
 
 // add a command to login that uses a session, so the user will remain logged in throughout the test file vs. needing to log in before each example.
@@ -44,10 +45,10 @@ Cypress.Commands.add('login', (username, password) => {
 Cypress.Commands.add('customApiIntercept', ({
   action, alias, data, defaultFixture, emptyFixture, error, errorCaseStatusCode, loading, requestURL
 }) => {
-  cy.intercept(action, scientistApiBaseURL + requestURL, (req) => {
+  cy.intercept(action, `${scientistApiBaseURL}${requestURL}`, (req) => {
     switch (true) {
       // reply with an empty response: both data and error will be undefined.
-      case loading: req.reply()
+      case loading: req.reply({})
       break
 
       // error will be defined
@@ -66,4 +67,4 @@ Cypress.Commands.add('customApiIntercept', ({
       break
     }
   }).as(alias || 'customIntercept')
-})
+})