Multiple claimants:
  - Only recognise routes explicitly managed by ClaimTransitionManager.
    Before unrecognised routes would 500 because the corresponding
    form class didn't exist. Now 404.
  - Fix routes so that they're hyphenated, e.g. /apply/additional-information
    fixes #296
  - Forms always PUT to the same URL as for GET, e.g /apply/claimant
  - MultiplesController, a subclass of ClaimsController is used to
    support non-destructive addition of claimants
  - Allow a la carte destruction of addtional claimants
  - Destroy all additional claimants if the user chooses "No"
Multiple claimants:
  - Only recognise routes explicitly managed by ClaimTransitionManager.
    Before unrecognised routes would 500 because the corresponding
    form class didn't exist. Now 404.
  - Fix routes so that they're hyphenated, e.g. /apply/additional-information
    fixes #296
  - Forms always PUT to the same URL as for GET, e.g /apply/claimant
  - MultiplesController, a subclass of ClaimsController is used to
    support non-destructive addition of claimants
  - Allow a la carte destruction of addtional claimants
  - Destroy all additional claimants if the user chooses "No"
styled add additional person link/button
added mulitple claimants ui changes
added remove claimant link functionality.
fixed merge conflicts
Merge pull request #295 from ministryofjustice/feature/multiple-claimants

Add multiple claimants to the flow (WIP)
Adds session expiration check on requests under the claim and review paths
Adds a client side session prompt and count down allowing a user to refresh the session or ultimately timeout and expire.
Assign user session routes via enumeration
Assert we don’t expire sessions on the applications home page.