Bump firtool-resolver to 1.1.0

[jackkoenig]

This is sort of an BugFix to an unreleased API (added after 6.0.0-RC1), see the Release Notes for how this changes the behavior of FIRTOOL_PATH in a desirable way.

Contributor Checklist

• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
• Did you delete any extraneous printlns/debugging code?
• Did you specify the type of improvement?
• Did you add appropriate documentation in docs/src?
• Did you request a desired merge strategy?
• Did you add text to be included in the Release Notes for this change?

Type of Improvement

• Bugfix
• Dependency update

Desired Merge Strategy

• Squash

Release Notes

The logic for

• If FIRTOOL_PATH is set, the --version regex failing no longer will return fail, instead it will set version to <unknown>.
• If FIRTOOL_PATH is set and something fails (firtool not found or cannot execute the binary), then the error will be returned rather than firtool-resolver falling back to fetching the default version.
• Errors from running firtool will be logged and returned rather than unconditionally turned into "Firtool binary not on FIRTOOL_PATH".

Reviewer Checklist (only modified by reviewer)

• Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
• Did you mark the proper milestone (Bug fix: 3.5.x, 3.6.x, or 5.x depending on impact, API modification or big change: 6.0)?
• Did you review?
• Did you check whether all relevant Contributor checkboxes have been checked?
• Did you do one of the following when ready to merge:
  • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
  • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

[dtzSiFive]

I have not performed the reviewer checklist, apologies.

However, I did test that this works for me using FIRTOOL_PATH pointing to a firtool with a non-release-tag firtool version string, as well as when not setting FIRTOOL_PATH and the downloaded executable does not work (producing nice diagnostic).

LGTM, thanks!