feat(tracing): improved tracing for persisters and requests

[icyphox]

This patch introduces tracing for persisters and requests.

Checklist

• I have read the contributing guidelines.
• I have referenced an issue containing the design document if my change
  introduces a new feature.
• I am following the
  contributing code guidelines.
• I have read the security policy.
• I confirm that this pull request does not address a security
  vulnerability. If this pull request addresses a security. vulnerability, I
  confirm that I got green light (please contact
  [email protected]) from the maintainers to push
  the changes.
• I have added tests that prove my fix is effective or that my feature
  works.
• I have added or changed the documentation.

[hperl]

I see that we are repeating the package and function name in this and other functions. I wonder if it would make sense to ask the runtime for that information instead, so that this information does not get out-of-sync in case we rename or move the functions. WDYT?

func spanNameOfCurrentFunction() string {
	pc, _, _, ok := runtime.Caller(0)
	if !ok {
		return "unknown"
	}
	if f := runtime.FuncForPC(pc); f != nil {
		return f.Name()
	}
	return "unknown"
}

[icyphox]

Nifty, but am I using it correctly? (Looks to be returning its own name): https://go.dev/play/p/Aa0yIFb3cjq
I remember experimenting with this idea previously, this was my PoC:

func spanName() {
	pc := make([]uintptr, 15)
	n := runtime.Callers(2, pc)
	frames := runtime.CallersFrames(pc[:n])
	frame, _ := frames.Next()
	fmt.Println(frame.Function)
}

// Prints:
// module/package.Foo

Perhaps I'll create a separate PR for it (should be in ory/x anyway).

[icyphox]

Ah, it should be runtime.Caller(1) in your example.

[zepatrik]

Nice, just some minor questions.
Is there maybe a linter we can use to ensure the span name and function name are consistent?