feat(openid-connect plugin): support configuring session name and path

[damoshushu]

Description

In some case, we need to provide different identity providers for different paths within the same host, however apisix uses the name "session" to store the cookie, which will cause the cookie be overwritten by the following authentication action.

for example,

• uri: /web/app1 use oidc with client_id_a
• uri: /web/app2 use another oidc with client_id_b

if we access /web/app1, after authentication, the auth cookie will be stored as "session", then we access /web/app2, after authentication, the auth cookie will be overwritten with client_id_b. Now we access /web/app1, the client_id_b's token will be passed to app1.

Fixes # (issue)

#11229
#9834

Checklist

• I have explained the need for this PR and the problem it solves
• I have explained the changes or the new features added to this PR
• I have added tests corresponding to this change
• I have updated the documentation to reflect this change
• I have verified that this change is backward compatible (If not, please discuss on the APISIX mailing list first)

[shreemaan-abhishek]

instead of configuring name of the cookie for all plugins, can we append the path to the cookie name?

[github-actions]

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If you think that's incorrect or this pull request should instead be reviewed, please simply write any comment. Even if closed, you can still revive the PR at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions.

[github-actions]

This pull request/issue has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.