Add handling of previously installed bicep executable

[guidooliveira]

The compileBicep and compipeBicepParams functions in helpers/file.ts will try to install bicep from github.com regardless of whether it is already available on the runner's PATH. This makes the action unusable in runners that have no direct internet access.

As a workaround I've added to the functions the following:

// needs import { which } from "@actions/io";
const bicepFilePath: string = await which('bicep', false); 

const bicepPath = !bicepFilePath || bicepFilePath.trim() == "" ? await Bicep.install(tmpdir()) : bicepFilePath; 

Since bicepPath already is being used, I just added the option to look for each locally before attempting to install it.

If you find that this is worth implementing, this is how I got it working with a local fork.

[anthony-c-martin]

I think the ask makes lot of sense, but I think it needs to be a user opt-in, rather than default behavior, or it may confuse people.

The logic above looks good to me, as long as we add an action parameter to enable it (e.g. use-bicep-from-path)

[SydneyhSmith]

Related issue #209