curiefense's configuration does not applied dynamically to curieproxy(istio) pod.

[KoJJang]

Describe the bug
Configs not applied to curieproxy dynamically.
I changed some configs(global-filter) to check some features, and publish them successfully. Then, I can check istio pod have modified config file. But actual response from proxy did not change.

What I was trying to verify was this

1. in a situation that normally works well with 200 responses, the
2. when I tried to drop it along with other responses through the global filter setting,
3. the file in the path /cf-config/current/config/json/globalfilter-lists.json in the curieproxy pod was changed to what I had set it to,
4. the actual response did not change.
5. but after restarting curieproxy pod, it worked as I wanted (different response than 200)

To Reproduce
Steps to reproduce the behavior:

1. Create new global filter to drop packet that have "foo: bar" header with 427 response code.
2. Save -> Publish
3. Check /cf-config/current/config/json/globalfilter-lists.json path in pod and there is expected config file.
4. Client's request still respond 200 code.
5. Restart curieproxy pod
6. From then, client's request respond 427 code.

Expected behavior
Dynamically changing the behavior of the actual curieproxy as settings change

Desktop (please complete the following information):

• OS: private k8s cluster
• Version: v1.21.2