Build error if the missing -bs-super-error flag is in a dependent package

[mununki]

When we cleaned up super-error, we removed the compiler's -bs-super-error flag, but I ran into an issue where it wouldn't build if a dependent package used that flag. I was wondering if we could bring it back and deprecate it first.

FAILED: src/ReForm.ast
unknown option: '-bs-super-errors'.
Usage: bsc <options> <files>
Options are:
Options:
  -w                        <list>  Enable or disable warnings according to <list>:
                            +<spec>   enable warnings in <spec>
                            -<spec>   disable warnings in <spec>
                            @<spec>   enable warnings in <spec> and treat them as errors
                            <spec> can be:
                            <num>             a single warning number
                            <num1>..<num2>    a range of consecutive warning numbers
                            default setting is +a-4-9-20-40-41-42-50-61-102
  -bs-g                     Debug mode
  -bs-D                     Define conditional variable e.g, -D DEBUG=true
  -e                        (experimental) set the string to be evaluated in ReScript syntax
  -v                        Print compiler version and location of standard library and exit
  -version                  Print version and exit
  -warn-help                Show description of warning numbers
  -warn-error               <list>  Enable or disable error status for warnings according
                            to <list>.  See option -w for the syntax of <list>.
                            Default setting is -a+5+6+101+109

FAILED: cannot make progress due to previous errors.

[cristianoc]

CC @cknitt

[cknitt]

Hmm, yes, there are probably a lot of libs out there that still have this flag set. Deprecating instead of removing sounds good to me.

I'll wait with the alpha.6 release for this then.

[mununki]

I'll fix it soon.

[mununki]

@cknitt #6243 PR is merged.