chore: fix go.mod add go.work

[ccoVeille]

The relative path in go.mod used in file datasource modules
This caused an error when the repository was named something else than "gofr".

Please note, I'm not even sure there is a logic to use relative path now the dev is over.

Also add missing go.work files
I'm not even sure how the project could be managed without this.
I'm sure there are some part of the CI that could be deleted now the go.work file is present

[ccoVeille]

Please note the go test ./... and golangci-lint run are now launched on everything as they should

so the CI about "sub modules" should be removed

Let's talk about it here.

[ccoVeille]

I think the next step should be done:

• remove the relative path hack in pkg/gofr/datasource/file/*/go.mod
• remove everything in CI about looking for go.mod files and perform go test or golangci-lint run

Everything works without them now there is a go.work file

https://go.dev/doc/tutorial/workspaces

[ccoVeille]

@Umang01-hash could you take back this one

As I told you I'm facing personal issue.

It's just a matter of test.

I would like this to be merged before the following ones:

• Add support for NATS-KV (key-value) store #1452
• En/arango db support #1429
• Open ai wrapper #1371

Code is ready.

[Umang01-hash]

@Umang01-hash could you take back this one

As I told you I'm facing personal issue.

It's just a matter of test.

I would like this to be merged before the following ones:

• Add support for NATS-KV (key-value) store #1452
• En/arango db support #1429
• Open ai wrapper #1371

Code is ready.

Sure @ccoVeille i will take it up after these PR's are merged.

[ccoVeille]

I think the next step should be done:

• remove the relative path hack in pkg/gofr/datasource/file/*/go.mod
• remove everything in CI about looking for go.mod files and perform go test or golangci-lint run

Everything works without them now there is a go.work file

https://go.dev/doc/tutorial/workspaces

I'm no longer sure about the next step (at least the second one)

There is an interesting discussion here

go-testfixtures/testfixtures#257 (comment)

That may affect the way the CI changes I was asking to remove might have to stay.