Skip building the project for the SQL validation if it isn't needed

[jsnb-devoted]

Change description

Updates the SQL validation check to skip the lookml_models API call if the explores argument is provided to the spectacles sql command.

A non cache hit call to this API takes 20+ minutes to return and in cases where we have made the determination of what explores we want to test -- the API isn't actually necessary.

This change effectively detects whether the explores argument has been provided and if the parameters contain any wildcard selections. If the arguments are single explores (my_model/my_explore) then it skips the API call and builds project with just the provided models/explores.

Type of change

• Bug fix (fixes an issue)
• New feature (adds functionality)

Related issues

Checklists

Security

• Security impact of change has been considered
• Code follows security best practices and guidelines

Code review

• Pull request has a descriptive title and context useful to a reviewer

[DylanBaker]

Hey @jsnb-devoted. Thanks for splitting this out.

While I totally understand how this makes sense for your use case, I think it probably leads to some complications on our end, particularly for how this works in the hosted application.

Any run of Spectacles is typically scoped to a single project (via the --project flag). In a world where we don't build the project and just take explores directly from the filters, you could conceivably be testing explores from multiple different projects (whether they import each other or not). This behaviour isn't necessarily problematic in and of itself, but it would probably need to come with a broader rethinking of how we scope each validator at the project level. I'd be open to exploring this, but I think I'd need @joshtemple's input and we would probably need to work at it a little. Happy to do so, but for transparency we likely won't have time to work on it for at least a few weeks.