Update FiraCode Nerd Font

[julienma]

After making all changes to the cask:

• brew cask audit --download {{cask_file}} is error-free.
• brew cask style --fix {{cask_file}} reports no offenses.
• The commit message includes the cask’s name and version.
• The submission is for a stable version or documented exception.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• brew cask install {{cask_file}} worked successfully.
• brew cask uninstall {{cask_file}} worked successfully.
• Checked there are no open pull requests for the same cask.
• Checked the cask was not already refused.
• Checked the cask is submitted to the correct repo.

[julienma]

This update downloads the font files directly, instead of the repo release which is way outdated.

This fixes 2 issues:

• use latest version of the font (1.206 -> 2.0), cf. Update Fira Code Font to 2.0 ryanoasis/nerd-fonts#424
• use real font name (Fura -> Fira), cf. Change Fura to Fira ryanoasis/nerd-fonts#356

[vitorgalvao]

No need to use svn, you can download the master zip.

But a better solution is to ask upstream to cut a new release. We prefer that to workarounds.

[julienma]

Thanks for the reply.

I’ll ask for a new release, but I’m not confident: current milestone is past due 2 years, and considering there are dozens more fonts in this repo, it’d involve a lot more work than cutting a new release just for a single font.

Re: downloading the master zip, would that be better than selectively downloading files via svn? There are dozens of fonts in that repo, it seems a waste of bandwidth to download a big zip just to keep a handful of files.

[parkerbxyz]

Re: cutting a new release, the commit message here seems to indicate a new release may be imminent: ryanoasis/nerd-fonts@fa69496.

[ryanoasis]

Release has been cut, not sure if this will change what you want to do here, just an FYI

[vitorgalvao]

@ryanoasis Thank you.

@julienma It’s fine if you prefer to close this PR and open a new one. Do whatever’s most convenient.

[julienma]

Thank you @ryanoasis :)

@vitorgalvao I've updated the cask using cask-repair, PR is here: #1944. Closing this one. Thanks!