feat: geolocation setter in sendgrid-python for GDPR compliance

[manisha1997]

feat!: Geolocation setter for GDPR compliance

Checklist

• I acknowledge that all my contributions will be made under the project's license
• I have made a material change to the repo (functionality, testing, spelling, grammar)
• I have read the Contribution Guidelines and my PR follows them
• I have titled the PR appropriately
• I have updated my branch with the main branch
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation about the functionality in the appropriate .md file
• I have added inline documentation to the code I modified

If you have questions, please file a support ticket.

[shrutiburman]

LGTM

[manisha1997]

@tbischel, What will be the precedence of the host and data_residency.
In case, the user uses both set_host and set_data_residency, we are setting host based on the latest input.

sendgrid-python/test/unit/test_sendgrid.py

Line 19 in 639f14e

def test_host_with_host_first_eu_region_second(self):

,

sendgrid-python/test/unit/test_sendgrid.py

Line 25 in 639f14e

def test_host_with_eu_first_host_second(self):

Can you please clarify if this is correct precedence?

[gladysmae08]

CR

[tbischel]

regarding precedence:
I think if they explicitly call the setters, it makes sense to respect the latest called. I think if they pass region and host in the constructor at the same time, we should throw an error if they conflict.

[manisha1997]

Makes sense Tyler, thanks.
Will introduce the changes accordingly.

[manisha1997]

@tbischel, we decided to remove region and only have a data residency setter.
We removed the set_host as we don't want to expose the function right now #1073 (comment).
Can you please review the changes

[tbischel]

minor nit with the print placement, but other than that LGTM

[tiwarishubham635]

LGTM!

[tbischel]

LGTM