Update drupalci.yml to not half on eslint fail!

Let's see if this appeases the test bot...

Updated issue title and approach! Can't believe I overlooked this testing configuration!

I'm only committing #4 w/o a review step because it only affects internal build steps, and only against the 4.0.x branch (presently failing CI).

This isn't my typical workflow. Drupal CI is rather cumbersome to tame...as can be seen with the differences in behavior between patch testing vs branch testing :-(.

4.0.x-dev is now green! Full steam ahead.

Automatically closed - issue fixed for 2 weeks with no activity.