fix: expose verify option through client options

[silentworks]

What kind of change does this PR introduce?

Bug fix to expose verify via the ClientOptions through the httpx_options config.

from supabase import create_client, ClientOptions

supabase = create_client(
  url, 
  anon_key, 
  options=ClientOptions(httpx_options={"verify": False})
)

What is the current behavior?

There is no way to set the verify flag from the supabase python library.

What is the new behavior?

You can now set the verify flag from the supabase python library

Additional context

#1086

[coveralls]

Pull Request Test Coverage Report for Build 14176586988

Details

• 8 of 9 (88.89%) changed or added relevant lines in 2 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.03%) to 85.856%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
supabase/lib/client_options.py	5	6	83.33%

Files with Coverage Reduction	New Missed Lines	%
supabase/lib/client_options.py	1	84.81%

Totals
Change from base Build 14094370943:	0.03%
Covered Lines:	346
Relevant Lines:	403

---

💛 - Coveralls

[silentworks]

Do not merge as yet, we are looking into a better option which won't need us replicating httpx options.

[grdsdev]

blocking until better option

[silentworks]

Closing in favor of #1117