middleware/proxy - 🐛 fix: solve data race in middleware/proxy's test

[li-jin-gou]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Explain the details for making this change. What existing problem does the pull request solve?

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• For new functionalities I follow the inspiration of the express js framework and built them similar in usage
• I have performed a self-review of my own code

Commit formatting:

Use emojis on commit messages so it provides an easy way of identifying the purpose or intention of a commit. Check out the emoji cheatsheet here: https://gitmoji.carloscuesta.me/

[li-jin-gou]

I found that the unit test I wrote before had datarace between use WithClient() and cli = client.

• https://github.com/gofiber/fiber/blob/master/middleware/proxy/proxy.go#L114 set client
• https://github.com/gofiber/fiber/blob/master/middleware/proxy/proxy_test.go#L401 get client

can I use mutex or atomic here or remove t.Parallel()?

[efectn]

I found that the unit test I wrote before had datarace between use WithClient() and cli = client.

• https://github.com/gofiber/fiber/blob/master/middleware/proxy/proxy.go#L114 set client
• https://github.com/gofiber/fiber/blob/master/middleware/proxy/proxy_test.go#L401 get client

can I use mutex or atomic here or remove t.Parallel()?

I think mutex

[li-jin-gou]

I found that the unit test I wrote before had datarace between use WithClient() and cli = client.

• https://github.com/gofiber/fiber/blob/master/middleware/proxy/proxy.go#L114 set client
• https://github.com/gofiber/fiber/blob/master/middleware/proxy/proxy_test.go#L401 get client

can I use mutex or atomic here or remove t.Parallel()?

I think mutex

thanks