Consider allowing bypassing validation of firmware filename

[bruno-f-cruz]

The current pipeline to upload firmware files to device relies on validating the filename string to a template. e.g:

Behavior-fw3.2-harp1.13-hw2.0-ass0.hex

The current parsing relies on a custom parsing regex:

harp/Bonsai.Harp/FirmwareMetadata.cs

Line 13 in eae1176

static readonly Regex MetadataRegex = new Regex("^(?<device>\\w+)-fw(?<firmware>\\d+\\.\\d+)-harp(?<core>\\d+\\.\\d+)-hw(?<hardware>(?:x|\\d+)\\.(?:x|\\d+))-ass(?<sequence>x|\\d+)(?:-preview(?<prerelease>\\d+))?$");

Recently, some files in harp-tech were found to have been misformatted (e.g. underscores instead of dashes) or missing information (e.g. no assembly).

One way to get around this is not to enforce the validation of the name, but simply to provide a warning to the user in the UI (or in the harp.toolkit) and allow users to force the update at their own risk.