Test for Menu access control

I've created a preliminary test for Menu access control. Right now, its a modified clone of the existing Taxonomy access control. It's ugly, there's duplicate functionality, etc., but it is there.

Some ways it departs from the existing Taxonomy test:

• It uses the "minimal" profile for testing. I'm pretty sure I had a reason for this, but I don't remember it now.
• Instead of using the Pages content type, a new content type is generated.
• An administer user is created and used to populate values through Drupal, like the created menu. See the "ugly" statement before. If there is an obvious way it should be changed, let me know.
• I've removed the section on machine_name renaming of Taxonomy. I don't think you can rename a menu's machine name?
• Converted most (all?) db_querys to abstract functions. Started with the new ones and then just did them all

The nodes are made with the following menu hierarchy.

/**
* Assign menu links for nodes.
* The hierarchy should four levels deep with two options per level
* A helpful diagram
*
* A
*   A1
*     A1a
*        A1a1
*        A1a2
*     A1b
*        A1b1
*        A1b2
*   A2
*     A2a
*        A2a1
*        A2a2
*     A2b
*        A2b1
*        A2b2
* B
*   B1
*     B1a
*        B1a1
*        B1a2
*     B1b
*        B1b1
*        B1b2
*   B2
*     B2a
*        B2a1
*        B2a2
*     B2b
*        B2b1
*        B2b2
*/

Currently, all of the tests appear to be passing. I'm fairly certain they all are passing properly.

I plan on extending the test to check for the issues in #1422868: Menu hierarchy - permissions descendancy and #1101638: Default menu form support. That said, it looks like my work schedule is going to be picking up soon, so I thought it'd be good to push up now. Patch in the next post.