PrivateMethodCheck: force programmers to introduce new class instead

[h1alexbel]

I think we should make private methods illegal to use, long-story-short, here is main reasons "why":

1. Private methods are not reusable between objects
2. Private methods are not testable

consider this example:

final class Cat {
  public void meow() {
    this.print();
  }
  
  private void print() {
  }
}

OOPCOP should fail this class with a message like this:

Private method detected in Cat.java[6]. Consider creating new class instead. It's both: reusable and testable, see: $blog link (PrivateMethodCheck)

also, it should be suppressible:

@SuppressWarnings("OCOP.PrivateMethodCheck")

@l3r8yJ what do you think?

[zoeself]

@h1alexbel thank you for reporting this. I'll assign someone to take care of it soon.

[zoeself]

@l3r8yJ this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2024-01-08T08:40:00.307453.

Estimation here is 60 minutes, that's how much you will be paid.

Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.

If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.

If you don't have time or simply don't want to work on this, you can always resign.

[l3r8yJ]

@h1alexbel good idea!

[h1alexbel]

@l3r8yJ please assign me

[l3r8yJ]

@zoeself reassign

[zoeself]

@zoeself reassign

@l3r8yJ didn't understand that, sorry.

[l3r8yJ]

@zoeself resign

[zoeself]

@zoeself resign

@l3r8yJ ok, I'll find someone else to take care of it.