Add support for Grove tb6612 fng

[max246]

What does this implement/fix?

I am working with this handy motor driver which can drive DC and Stepper motors : https://wiki.seeedstudio.com/Grove-I2C_Motor_Driver-TB6612FNG/
The good thing about this driver is the connectivity to be used over i2c rather than the usual hbridge and you can set the motor driver to standby to stop wasting power.

Methods implemented:

• grove_i2c_motor.motor_run
• grove_i2c_motor.motor_break
• grove_i2c_motor.motor_stop
• grove_i2c_motor.standby
• grove_i2c_motor.no_standby

At the current state, only DC motor is implemented but the code for the stepper motor is already ready to be expose via an action. I dont currently have a stepper motor so in my case I can only test a DC motor

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• [ x ] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Related issue or feature (if applicable): fixes

Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#2906

Test Environment

• ESP32
• ESP32 IDF
• [ x ] ESP8266
• RP2040

Example entry for config.yaml:

i2c:
  sda: 4
  scl: 5
  scan: true
  id: bus_a
grove_i2c_motor:
    id: test_motor
    name: motor_outside
    address: 0x14

switch:
  - platform: template
    name: open_vent
    id: open_vent
    optimistic: True
    on_turn_on: 
      then:
        - grove_i2c_motor.motor_run:
            channel: 1
            speed: 255
            direction: BACKWARD
            id: test_motor
        - delay: 10s
        - switch.turn_on: stop_motor
        - switch.turn_off:  open_vent



# Example config.yaml

Checklist:

• [ x ] The code change is tested and works locally.
• Tests have been added to verify that the new code works (under tests/ folder).

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in esphome-docs.

[probot-esphome]

Hey there @max246,
Thanks for submitting this pull request! Can you add yourself as a codeowner for this integration? This way we can notify you if a bug report for this integration is reported.
In __init__.py of the integration, please add:

CODEOWNERS = ["@max246"]

And run script/build_codeowners.py

_{^{(message by NeedsCodeownersLabel)}}

[jesserockz]

Generally looks good, just a few "tips" to align better with the codebase =)

[max246]

@jesserockz could this be approved?

[jesserockz]

Please add the actions to the test yaml file too

[max246]

Please add the actions to the test yaml file too

Should be all good now