feat: Option to search sass executable

[qdequippe]

I recently encountered this issue (see #84) during a deployment to a cloud environment. Since this specific environment restricts the installation of external binaries, I suggest adding a configuration option that allows the bundle to automatically download the appropriate binary during cloud build phase.

[bocharsky-bw]

Hm, I think we don't need that extra arguemnt, how about simplify the business logic in that method?

[bocharsky-bw]

Are you sure we need this searchBinary extra parameter? Why we can't just tweak this logic to:

Suggested change

	$binaryPath = $this->binaryPath;
	if (null === $binaryPath && $this->searchBinary) {
	$binaryPath = (new ExecutableFinder())->find('sass');
	}
	$binaryPath = $this->binaryPath;
	if (null === $binaryPath) {
	$binaryPath = (new ExecutableFinder())->find('sass');
	}

[qdequippe]

Yes I need it because in my case $this->binaryPath is null so $binaryPath will be null and an executable will be found.

I want to force $binaryPath to be null here, thanks to that SassBinary will download the binary locally.

[bocharsky-bw]

Hm, that's what I'm talking about... if you have binaryPath set to null, then this code should be enough for you to find the binary:

        $binaryPath = $this->binaryPath;
        if (null === $binaryPath) {
            $binaryPath = (new ExecutableFinder())->find('sass');
        }

Or you don't want the bundle to use your global sass locally and always download the new one?

[qdequippe]

Or you don't want the bundle to use your global sass locally and always download the new one?

yes that's it! :)