Resolve Style/StringConcatenation rubocop violations and enable the check for it

[bhushan354]

NOTE: Please review the pull request process before opening your first PR: https://github.com/WikiEducationFoundation/WikiEduDashboard/blob/master/CONTRIBUTING.md#pull-request-process

What this PR does

• Enable rubocop check for Style/StringConcatenation
• Ref Many rubocop linting rules are disabled. Choose one, enable it, and fix all violations #5297

Screenshots

Before:
< add a screenshot of the UI before your change >

After:
< add a screenshot of the UI after your change >

Open questions and concerns

< anything you learned that you want to share, or questions you're wondering about related to this PR >

[bhushan354]

Hi @ragesoss ,

I’ve been trying to resolve this issue and noticed that all recently opened PRs are failing this specific test. Here’s a screenshot for reference:

Do you have any leads on what might be causing this?

[ragesoss]

Thanks for opening this PR!

I think I prefer to keep these string concatenations as they are, rather than change any of the files, I will accept a PR that moves this rule to the 'permanent exceptions' section.

That failing test is one that sometimes fails for unknown reasons. @Formasitchijoh is currently working on a project to improve the test suite's reliability, and I think this test is on the list for investigation.

[ragesoss]

The PR should only include changes to the one file, and should only include a single commit.

[bhushan354]

@ragesoss i have reverted the changes in this PR itself , do you want me to create another PR or this one is fine?

[ragesoss]

This is okay, I will squash it. However, I generally prefer PRs that have a well-curated commit history, where only necessary commits are part of it.

[bhushan354]

Thanks for the help! I'll keep that in mind for next time.