Fix an error where conversion failed if securitySchemes are not defined

[dhwaneetbhatt]

Overview

This PR fixes an issue when RAML contains securitySchemes that could not be resolved.

RCA

When the spec did not have any securitySchemes but an existing resource references it via the securedBy parameter, it was throwing a referencing error as it was trying to do securitySchemes[securedBy].description, but since securitySchemes was an empty string, securitySchemes[securedBy] was undefined, leading to this error. This used to happen when creating auth object for the collection request.

Fix

• Only resolve auth object for collection when both securedBy and securitySchemes are not empty
• Even if both are non-empty, verify the existence of the description key via a safe check

Additional change - Test action runs only once for a PR. It runs on push only for the master and develop branches.