Added HttpDigestAuth ability to Telegram when sending photos

[tchellomello]

Description:

When creating an automation/script using notify/Telegram with URL photo support, it will not work if the webserver requires an HTTPDigestAuth.

For example, the new Amcrest firmware requires a HttpDigestAuth to download the camera snapshot.

Related issue (if applicable): fixes #7395

Example entry for configuration.yaml (if applicable):

#scripts.yaml
send_snapshot_telegram_driveway:
  alias: 'Send snapshot driveway camera'
  sequence:
    - service: notify.telebot
      data:
        title: "Driveway Motion"
        message: "There is a motion detected on the driveway"
        data:
          photo:
            - url: !secret amcrest_driveway_snapshot_url
              username: !secret amcrest_driveway_username
              password: !secret amcrest_driveway_password

Checklist:

If the code does not interact with devices:

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• Tests have been added to verify that the new code works.

[mention-bot]

@tchellomello, thanks for your PR! By analyzing the history of the files in this pull request, we identified @pvizeli, @fabaff and @icovada to be potential reviewers.

[pvizeli]

Please do it in same way as we do it inside generic camer

[balloob]

Let's put this PR on hold for now until #7294 gets merged

[tchellomello]

@pvizeli since the telegram component can be used for multiple purposes, instead of making setting a self._authentication value globally, I kept the same approach and kept the authentication as an attribute to be used like caption for example.

If you agree with that, I'll go ahead and modify the documentation explaining the new configuration:

send_snapshot:
  alias: 'send snapshot'
  sequence:
    - service: notify.telegramBot
      data:
        title: 'Snapshot Cam'
        message: 'Sending snap from cam'
        data:
          photo:
            - url: !secret amcrest_url
              caption: "Snapshot Amcrest"
              authentication: "digest"
              username: !secret amcrest_username
              password: !secret amcrest_password

If authentication is not present, then it will try basic auth.

[tchellomello]

@balloob sounds good.

@pvizeli @balloob Thanks for your help.

[pvizeli]

Yeah, don't do that global, make it per request and default Basic 👍

[tchellomello]

@pvizeli yes, so that is the way it is now. As @balloob mention, let me know if that looks good after the PR #7294

Thank you!

[balloob]

Alright, closing this one for now then