feat(eslint): add linting rules for test describe depth

[gracetxgao]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/develop/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Fixes: #122

What is the new behavior?

Maximum describe() depth of 3 set for tests.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[damienwebdev]

This is awesome! @griest024 do you think we should set depth to 4 as warning, and 5 as error? I only see a few with 5, but many more with 3/4.

[griest024]

@damienwebdev 5 as an error sounds good. Can we mix error and warning values for the same rule? Afaik eslint does not allow for this.

[damienwebdev]

daffodil/tools/eslint/config/package.json

Line 14 in d41bc5a

"eslint-plugin-jasmine": "0.0.0-PLACEHOLDER",

needs an update for the dependency as well

[damienwebdev]

lgtm. Needs @griest024 approval for merge.

[griest024]

lgtm

[griest024]

needs a rebase

[damienwebdev]

@gracetxgao Needs another rebase.

[damienwebdev]

lgtm