Inspired by some issues noticed in:
https://issuetracker.google.com/35820879

---

We have an old database (last updated 2013-11-27, with occasional backports over the years). We can continue to do piecemeal backports as fixes come up, or we can choose to upgrade the whole thing. I see numerous additions and corrections since we've last upgraded the database, so there should definitely be an upside. (For one, it would have already fixed the above linked bug, years ago.)

I'd like to collect any reasons people might have for/against this, as it's not clear whether the age of our database is intentional, or just the path of least resistance.

A few notes:

* https://wireless.wiki.kernel.org/en/developers/regulatory/processing_rules
* We should probably collect a set of tests to run for this sort of thing. More details below.

---

Testing:

network_WiFi_Regulatory: according to kirtika@, this "claims to test channel switch, a feature we dont have and dont support". So I guess we ignore this...

network_WlanRegulatory: confusingly similarly-named to the above test. It seems to do some basic testing, but notably it doesn't actually check that the rules took hold properly. For one, it seems that the kernel has semi-recently starting rejecting certain malformed regulatory info passed from userspace. So while we might "change country codes", the crda user-space helper might fail. Can we improve the tests for this?

Association: none of the above actually tests that a device can associate to any non-default/US APs. I see some notes about prior manual testing to "associate to an AP exporting a non-default 802.11d country code. Ensure that "iw reg get" shows this country code and the correct rules." Can we automate this?

This may affect the Jetstream product family. We should make sure that any upgrades here don't negatively impact them.