Allow multiple version ranges for traced field offsets

[MrAlias]

Currently, our offset data model expects a continuous range of supported field offsets and therefore only allows one version range per:

opentelemetry-go-instrumentation/internal/pkg/inject/data.go

Lines 24 to 25 in 82c7468

	// TrackedStruct maps fields names to the tracked fields offsets.
	type TrackedStruct map[string]TrackedField

As has been shown in #273 where there is a break in the support of gRPC (

opentelemetry-go-instrumentation/internal/pkg/inject/offset_results.json

Lines 5 to 28 in 949e8a3

	{
	"versions": {
	"oldest": "1.0.0",
	"newest": "1.0.4"
	},
	"offsets": [
	{
	"offset": 8,
	"since": "1.0.0"
	}
	]
	},
	{
	"versions": {
	"oldest": "1.3.0",
	"newest": "1.59.0-dev"
	},
	"offsets": [
	{
	"offset": 8,
	"since": "1.3.0"
	}
	]
	}

), it is not always the case that we will be able to support continuous ranges of package versions.

We should instead define the TracedStruct as:

type TrackedStruct map[string][]TrackedField

And track each version range.

Related to #271
Blocked by #307 (once merged we can fix this in a single spot)