Fix endpoint for updating message templates

[Ahriman]

Hello,

I encountered an error while trying to update a message template and found the root cause.

The library currently uses the endpoint https://graph.facebook.com/API_VERSION/WABA_ID/message_templates/TEMPLATE_ID to update a template. However, according to the documentation, the correct endpoint should be https://graph.facebook.com/API_VERSION/TEMPLATE_ID.

Documentation reference:

WhatsApp Business Management API - Message Templates

I have made the necessary changes to correct this endpoint. Since this is a small change, I believe it should be straightforward to review.

Greetings.

[github-actions]

Hello and welcome! We are excited to see your first pull request and appreciate your contribution to our project. Our team is reviewing your changes and we will provide feedback as soon as possible. Thank you for taking the time to improve our project and we look forward to working with you!

[Ahriman]

It's my fisrt pull request on GitHub and I think that is needed to review because it can break using previous API versions

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.77%. Comparing base (8e20a52) to head (12920af).

Additional details and impacted files

@@            Coverage Diff            @@
##               main     #189   +/-   ##
=========================================
  Coverage     85.77%   85.77%           
  Complexity      512      512           
=========================================
  Files           164      164           
  Lines          1244     1244           
  Branches         12       12           
=========================================
  Hits           1067     1067           
  Misses          158      158           
  Partials         19       19           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[skennic]

Hello @Bindambc,

I stumbled upon the same problem and wondered why this PR is not yet merged as it seems to fix the changed API URI.
Can you take a look again?

Kind Regards
Ken-Nic