Redirect to campaign detail upon entry creation

[JasonGadoury]

Description

Closes #500

Once a campaign entry or dm entry is successfully created, the user is now redirected to the campaign detail page instead of the character detail or dm entry index pages respectively.

To test:

1. Seed database
2. Create a dm entry for a campaign the signed in user is dm for
   (if they are not dm for any campaign, create a campaign and assign them dm)
3. Observe that you have been redirected to campaign detail page
4. Create an entry for a campaign the signed in user is participating in with a character
5. Observe that you have been redirected to campaign detail page

[codeclimate]

Code Climate has analyzed commit 90b737e and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (90% is the threshold).

This pull request will bring the total coverage in the repository to 91.6%.

View more on Code Climate.

[JasonGadoury]

Looks like I have a code smell for having too many redirects in the store function. Each redirect is chosen based on the type of entry being created (invalid gm entry, regular or dm entry with campaign, regular or dm w/o campaign...). The two options are to either ignore it or sacrifice one of the redirects. Thoughts? @m-triassi

[m-triassi]

@JasonGadoury there's a third option, instead of returning, assign the route name string to a variable that changes based on the conditions, and then pass that variable to the route() function
something like:

if ($x == "Condition A") {
    $redirect = 'campaign.show';
    $extraData = [...];
} elseif ($x == "Condition B") {
    $redirect = 'character.index'; 
    $extraData = null;
}

return redirect()->route($redirect, $extraData);

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

0.0% Coverage
0.0% Duplication

[m-triassi]

This works, some things to consider for refactor, but I'll handle that at a later date.

[m-triassi]

Typically i'd avoid nesting control flow logic more than 1 layer deep if possible. Since we don't really have the luxary of time, ill just say this is a refactor target and move on