Improve error handling and remove panic-prone code

[hatoo]

• Replace unwrap() calls with proper error handling in certificate generation
• Convert Ok(..) else patterns to match statements with error context
• Standardize error logging with consistent messages
• Handle TLS connection errors gracefully instead of panicking
• Fix authority parsing to handle invalid values without crashing

🤖 Generated with Claude Code

[Copilot]

Pull Request Overview

This PR improves error handling and removes panic-prone code by replacing unwrap() calls with proper error propagation and logging.

• Certificate generation now returns a Result with propagated errors instead of panicking.
• TLS connection accept and upgrade failures are handled gracefully with appropriate logging.
• The default client now carefully converts host values and parses headers without panicking.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/tls.rs	Updated certificate generation to use error propagation with ? operators.
src/lib.rs	Replaced unwrap-based patterns in async connection handling with error logs.
src/default_client.rs	Improved error handling in TLS host conversion and header insertion.

[Copilot]

Consider including the actual host value in the error message (e.g., 'Failed to generate certificate for host {}: {}') to provide more context for debugging.

Suggested change

	generate_cert(host, root_cert.borrow()).map_err(|err| {
	tracing::error!("Failed to generate certificate for host: {}", err);
	}).ok()
	})
	} else {
	generate_cert(host, root_cert.borrow())
	.map_err(|err| {
	tracing::error!("Failed to generate certificate for host: {}", err);
	generate_cert(host.clone(), root_cert.borrow()).map_err(|err| {
	tracing::error!("Failed to generate certificate for host {}: {}", host, err);
	}).ok()
	})
	} else {
	generate_cert(host, root_cert.borrow())
	.map_err(|err| {
	tracing::error!("Failed to generate certificate for host {}: {}", host, err);