Tests for various challenges are too strict about line breaks before method calls (part 2)

Not all of the challenges listed in #35090 were fixed by #35093. This issue is for the remaining challenges that the aforementioned PR did not modify.

The problem

The tests for various challenges are too strict about line breaks before method calls.

E.g. something like this passes:

document.getElementById( 'getMessage' )
      .onclick = function() {};

But this causes the tests to fail:

document
      .getElementById( 'getMessage' )
      .onclick = function() {};

Affected challenges

• “JSON APIs and Ajax: Access the JSON Data from an API”:

console.log(
  json[2]
    .codeNames[1]
);

• “JSON APIs and Ajax: Get Geolocation Data to Find A User’s GPS Coordinates”:

if ( navigator.geolocation ) {
  navigator.geolocation.getCurrentPosition(
    pos => {
      document.getElementById( 'data' )
        .innerHTML =
          'latitude: ' +
          position.coords.latitude +
          '<br />longitude' +
          position.coords.longitude;
      }
    );
}

Browser and OS info

• Browser Name: Firefox Developer Edition
• Browser Version: 66.0b9
• Operating System: Antergos Linux

[RandellDawson]

I have asked @ValeraS who has a very solid understanding of what helper utilities to which we have access.

[RandellDawson]

@Ensive We have concluded for now, we will have to write our own as they do not want to add another package to the library. I think we should actually consider how we can test these types of challenges without resorting to using regex. For example, we should be validating that the code written actual returns the correct JSON response. That is the true test. We might look for a few key methods with regex, but not complete lines of code.