feat(http): add request and response tracing behind feature flag

[amrbashir]

closes #2055

Users can use tauri-plugin-log or CrabeNebula devtools to inspect the requests and responses.

[github-actions]

Package Changes Through 6ff999f

There are 15 changes which include upload with minor, upload-js with minor, deep-link with patch, deep-link-js with patch, log-plugin with patch, log-js with patch, fs with patch, fs-js with patch, http with patch, localhost with minor, opener with major, opener-js with major, positioner-js with minor, positioner with minor, sql with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
api-example	2.0.5	2.0.6
api-example-js	2.0.2	2.0.3
deep-link-example-js	2.0.0	2.0.1
deep-link	2.0.1	2.0.2
deep-link-js	2.0.0	2.0.1
fs	2.0.3	2.0.4
fs-js	2.0.2	2.0.3
dialog	2.0.3	2.0.4
opener	1.0.0	2.0.0
opener-js	1.0.0	2.0.0
http	2.0.3	2.0.4
localhost	2.0.1	2.1.0
log-plugin	2.0.2	2.0.3
log-js	2.0.0	2.0.1
persisted-scope	2.0.3	2.0.4
positioner	2.0.2	2.1.0
positioner-js	2.0.1	2.1.0
single-instance	2.0.1	2.0.2
sql	2.0.2	2.0.3
upload	2.1.0	2.2.0
upload-js	2.1.0	2.2.0

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[FabianLars]

iirc in tauri we're using tracing in tauri (and log in cli stuff). i think that makes sense here too? I also still use log in my projects but i hear again and again that tracing should be used instead especially in async contexts.