Make Menu Update to 1.10 not immediately require update.php

[quicksketch]

Describe your issue or idea

Follow-up to #225, in which menu items were made translatable.

Right now when updating from 1.9 to 1.10 (1.x dev version), the entire site is broken until update.php is run, because a query to the "menu_links" table is looking for a non-existent "langcode" column.

Steps to reproduce (if reporting a bug)

• Install Backdrop 1.9.x
• Update the code to 1.x
• Visit the site.

Actual behavior (if reporting a bug)

• At this point it is not possible to log in, which makes it difficult to run update.php

Expected behavior (if reporting a bug)

• You should still be able to use the site until update.php is run.

[quicksketch]

I added a PR at backdrop/backdrop#2189 that makes it so that if the menu fails to be built, the exception will be caught and the page is allowed to render anyway. However, this has substantial downsides that all menus will simply disappear from the page if no cache is present, including the admin bar menu. However, it's still an improvement as the user can log in, and once logged in the status notification dot still shows up and takes the user to the status report page, where they can see updates need to be run.

[herbdool]

@quicksketch this works--it's much better than getting a fatal error.

[quicksketch]

Yup, that's what I got as well. I actually had the admin menu working fine because it was cached, it was only after I intentionally cleared the cache that the menu disappeared. Let's proceed with this, it's a low-impact change that is unlikely to have repercussions, since it doesn't actually change any behavior when things are correct, just catches any errors and works around it.