Enable running of JUnit tests from within IntelliJ with default config

[ham1]

Description

With the default IntelliJ config tests are not run in the bin or project root folder which meant tests didn't run without a custom run setting.

Motivation and Context

Makes running tests far easier in IntelliJ.

How Has This Been Tested?

Running a sample of unit tests in IntelliJ

Screenshots (if appropriate):

Types of changes

• Dev enhancement

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.

[codecov-io]

Codecov Report

Merging #334 into trunk will decrease coverage by <.01%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##              trunk     #334      +/-   ##
============================================
- Coverage     57.93%   57.93%   -0.01%     
- Complexity    10025    10026       +1     
============================================
  Files          1148     1148              
  Lines         73748    73752       +4     
  Branches       7321     7323       +2     
============================================
- Hits          42728    42725       -3     
- Misses        28539    28547       +8     
+ Partials       2481     2480       -1

Impacted Files	Coverage Δ	Complexity Δ
...st/src/org/apache/jmeter/junit/JMeterTestCase.java	31.25% <0%> (-0.81%)	10 <0> (ø)
...c/org/apache/jmeter/junit/JMeterTestCaseJUnit.java	9.83% <0%> (-0.34%)	3 <0> (ø)
...ocol/jms/org/apache/jmeter/protocol/jms/Utils.java	54.83% <0%> (-4.31%)	15% <0%> (ø)
...apache/jmeter/extractor/TestBoundaryExtractor.java	97.88% <0%> (ø)	17% <0%> (ø)	⬇️
...c/core/org/apache/jmeter/reporters/Summariser.java	86.15% <0%> (+0.76%)	19% <0%> (+1%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3a60f2b...e625f95. Read the comment docs.