Create Currents slug migration

Create a migration to add a 'slug' string field to store the Currents'
friendly ID.
Run Currents slug migration
Find Currents by their FriendlyID

Use a slugged version of the Currents' titles to find the record
instead of record ID numbers. This will additionally allow urls to
use the slugged title instead of the numbered IDs.
Explicitly state which 'form' partial to render

Be more specific as to which form partial should be rendered from the
admins' Current 'index' and 'edit' views.
Fix Admin Currents view specs variable assignment

  * Set test user as admin to appear in the possible 'admin_users'
    form-select.
  * Create a new current record to use for the form in the 'index'
    view.
  * Assign 'admin_users' with the test user record.
Add render expectations to Currents view specs

Expect the appropriate templates to be rendered.
Clean Admin Currents view specs whitespace

Remove superfluous empty line.
Fix form action method

Fix the expectation for which action will be assigned to the form in
the 'edit' view. The method should be routable to the Currents'
'update' action, not the route that would render the form all over
again.
Remove superfluous form tag

The tag should only be rendered once. The 'index' and 'edit' views each
have their own form tags that include the 'form' partial so that the
appropriate routes for editing/creating Currents can be specified.
Fix submission element class

Change the auto-generated template class for the submit button to use
bootstrap's 'form-group' instead of the unused 'actions.'
Fix Admin Currents edit form url

Add the current record ID for which current will be manipualted to the
url that will be used when submitting the form back to the application.
Without the record specified, the application can't complete the url to
include the ID of the Current.
Create 'current_pending' migration
Run 'curren_pending' migration

Update DB schema by running the new migration. The field will allow
admins to see ideas that have been created by users with a suggested
current to belong to.
Add helper method to get list of all currents

Add a global helper method to retrieve an array of all Currents ordered
by name. The array can be used in form selectors for assigning ideas to
currents by users and admins.
DRY Ideas controller

Create a separate method to handle saving the associations between
ideas and tags and currents whenever an idea is created or updated. One
caveat is that each time an idea is changed, it will have its current
pending status reset to 'true.'

TODO:
  * Add check to determine if associated current has been changed
    before setting the pending status. The status should not change if
    the user has not changed the idea's current.
Allow users to submit a suggested current association

Users can suggest a Current to associate their idea with upon Idea
creation or updating. Allow this field to pass Rails' strong
parameters.
Allow admins to set the 'current_pending' status

Admin users should be able to modify the 'current_pending' status of an
idea. Allow this field to be passed through Rails' strong parameters to
the controller.
Remove superfluous bootstrap container

Remove the extra container div to give a little more real estate to
work with.
Specify partial to render

Specify that a partial will be rendered and the exact path of the
partial. This allows the form to be passed as a local variable and
appended to the one created in the 'edit' template.
Remove superfluous bootstrap container

Similar to the 'edit' template, remove the extra container div to
reduce the amount of extra whitespace used on-screen.