Refactor of Strategies

[bryannolen]

This is a cleanup and refactor of the Strategies.

1. Move all strategies into seperate go packages to allow for easier expansion.
2. Break up HTTP handler into sub functions for ease of readability and eliminate copy-paste.
3. Migrate from deprecated library "golang.org/x/crypto/ssh/terminal" to "golang.org/x/term"
4. Cleanup up variable names to make for more readable code.
5. Add a new Strategy Configuration option - FallbackCommand - currently implemeted only for HTTP Strategy.

• This allows you to specific a Command to be executed if none of the other commands configured match.
• This is required as you may want to specify a number of specially targetted Commands, and have a catch all. The problem is that a golang range-over-slice is non deterministic, and the last entry in the config may not be processed last at run time.

Usage Example:

commands:
  - regex: "login"
    handler: "Unauthorized"
    headers:
      - "www-Authenticate: Basic"
      - "server: Apache"
    statusCode: 401
  - regex: "index"
    handler: "Welcome"
    statusCode: 200
fallbackCommand:
    plugin: "LLMHoneypot"
    statusCode: 200

=======
Checklist:

All Submissions:

• [ ✅ ] Have you followed the guidelines in our Contributing document?
• [ ✅ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. [ ✅ ] Does your submission pass tests?
2. [ ✅ ] Have you lint your code locally before submission?

Changes to Core Features:

• [ ✅ ] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ✅ ] Have you written new tests for your core changes, as applicable?
• [ ✅ ] Have you successfully run tests with your changes locally?

[mariocandela]

HI @bryannolen,
thanks for the contribution ❤️, I'll review it soon, these are busy days.
Thanks for your time
Cheers
Mario

[bryannolen]

I have merged in the History changes from 3.3.9 as well now too.