Fix error reading array that could be undefined in ows service

[ianwallen]

Fix error reading array that could be undefined in ows service

Without this fix the following error could be displayed in JavaScript console
Cannot read properties of undefined (reading 'length')

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[josegar74]

@ianwallen do you have a service that cause the issue and can be used for testing?

[ianwallen]

While I was testing the file uploads for #8427 in our environment which was based on GN 4.2.9 branch, I was seeing the error constantly showing up in the java console. I assumed that it was good practice to add a if (Array.isArray(layers)) { before using the array.
If it should never happen that layers is not an array and it is always defined then we can abandon this PR and I can raise a bug the next time I see the error occur.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}