Create top-level `contrib` directory to aggregate the `pkg/instrumentation/*`

[y1yang0]

We'd like to move pkg/instrumentation to contrib at the root of the repository (mv pkg/instrumentation contrib).

After this change, contrib will contain the hook implementations, while pkg will hold the core APIs they depend on. This creates a clearer separation of responsibilities.

However, to make this happen, here are the changes that I think will be necessary:

• Currently, only the pkg package is embedded (see export.go). We'll need to embed the contrib package as well. This is crucial to ensure that our tool can always inject code once downloaded, even in an offline environment.
• All other paths referencing pkg will need to be updated. This will be the bulk of the work.

[tushar1977]

Hi, i'd love to work on this issue. Could you assign this to me?

[y1yang0]

Thanks for your interest in this issue! It has now been assigned to you. Please be aware that the task can be quite challenging. We're looking forward to your contribution/pull request, and feel free to ask any questions in the discussion.

[tushar1977]

Thanks for your interest in this issue! It has now been assigned to you. Please be aware that the task can be quite challenging. We're looking forward to your contribution/pull request, and feel free to ask any questions in the discussion.

thanks for assigning this issue.
First i'll prepare and present the necessary changes and strucuture in next 1-2 days

[tushar1977]

@y1yang0 could you describe this issue in more detailed way?

[y1yang0]

@y1yang0 could you describe this issue in more detailed way?

Updated

[kakkoyun]

Let's tackle this after merging #156 and #160 It will create to many conflicts otherwise.

Also I think we should have instrumentation for the integration we (maintainers) maintain and instrumentation/contrib for the outside contributions.

[tushar1977]

Let's tackle this after merging #156 and #160 It will create to many conflicts otherwise.

sure

Also I think we should have instrumentation for the integration we (maintainers) maintain and instrumentation/contrib for the outside contributions.

you mean keeping pkg/instrumentation/contrib also?

[kakkoyun]

you mean keeping pkg/instrumentation/contrib also?

No, having /instrumentation and /instrumentation/contrib. For example, net/http and grpc instrumentation we try to add can go to instrumentation/http and instrumentation/grpc but in the feature we can have instrumentation/contrib/gin that is added by a community member.