Update: fix wrong indentation about catch,finally

[mysticatea]

What is the purpose of this pull request? (put an "X" next to item)

[X] Bug fix (template)

Tell us about your environment

• ESLint Version: master
• Node Version: 6.3.0
• npm Version: 3.8.9

What parser (default, Babel-ESLint, etc.) are you using?

• default

Please show your full configuration:

• nothing

What did you do? Please include the actual source code causing the issue.

I realized this while I was reviewing #7347.

$ eslint test.js --no-ignore --no-eslintrc --rule "indent:error" --fix

test.js is:

{
    try {
    }
catch (err) {
    }
finally {
    }
}

What did you expect to happen?

ESLint fixes the code to:

{
    try {
    }
    catch (err) {
    }
    finally {
    }
}

What actually happened? Please include the actual, raw output from ESLint.

ESLint fixed the code to:

{
    try {
    }
catch (err) {
}
finally {
}
}

What changes did you make? (Give an overview)

If catch/finally keywords are at the first on a line, indent rule reports wrong indentations.

The rule does not report indentations of those keywords, then the rule makes indentations of those blocks as based on the keywords. As a result, the indentations are wrong.

In a similar case, else keyword, the rule handles the keyword correctly.
This PR changes indent rule about catch and finally (and while of DoWhileStatement) keywords as the same way of else keyword.

semver-minor: this is a bug fix which increases warnings. The following code has been no warning before.

try {
    doSomething()
}
     catch (err) { /*ignore*/ }

Is there anything you'd like reviewers to focus on?

Is the place of this change right?
I wrote the code in the same place with the code of else keyword.

[eslintbot]

LGTM

[mention-bot]

@mysticatea, thanks for your PR! By analyzing the history of the files in this pull request, we identified @vitorbal, @valorkin and @gyandeeps to be potential reviewers.

[gyandeeps]

nit: I think we should stick to string concat here because this makes it hard to read in this particular scenario. (or maybe its just me)

[platinumazure]

Agreed.

[eslintbot]

LGTM

[mysticatea]

I updated as using string concatenations.

[eslintbot]

LGTM

[mysticatea]

I'm merging this PR since this is a good companion of brace-style rule's autofix.