Webflasher BindPhrase is not limited to a minimum of 6+ characters like ExpressLRS Configurator

ExpressLRS configurator restricts to a minimum of 6 characters for a Bind Phrase

WebUI does not and you can use 5 for example

This leads to users mistakenly mixing up things if using ExpressLRS for part and WebUI for others, and they often arent as confident double check UIDs etc, just dont understand why ExpressLRS wont let them use less than 6 when weblasher does and so use a different bindpharase thinking it will just trunkcate it.

Need to standardise these limist in all areas between WebUI and ELRS Configurator.

Start by comparing the WebUI bind-phrase validation with the minimum enforced by ExpressLRS Configurator. Trace where the WebUI accepts the bind phrase and identify the corresponding validation areas that need alignment; done means all relevant interfaces consistently require at least 6 characters.

Written by the indexing model from the issue text.