URL encode postgres credentials

[agrimrules]

When the postgres credentials contain charachters such as / and ?
we need to URL encode them so that they are processed correctly.

Resolves: #3901

What changed?
When using the postgres sql plugin, we need to URL encode the username/password if they contain characters like / and ?.

Why?
To support postgres passwords containing / and ? or other similar characters in them.

How did you test it?
Verified the following ways

1. Tested against local docker postgres with problematic passwords.
2. Added unit test to verify correct encoding.

Potential risks
postgres connectivity could break on older versions of postgres. (very unlikely)

Release notes
None.

Documentation Changes
None.

[longquanzheng]

Looks good to me. Thanks for fixing it!

[coveralls]

Pull Request Test Coverage Report for Build 819225dc-22f4-40f1-9d34-9b4c8b3eee7a

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• 80 unchanged lines in 16 files lost coverage.
• Overall coverage decreased (-0.04%) to 56.684%

---

Files with Coverage Reduction	New Missed Lines	%
service/history/queue/timer_queue_processor_base.go	1	78.6%
client/history/client.go	2	40.32%
client/history/metricClient.go	2	45.94%
common/task/weightedRoundRobinTaskScheduler.go	2	89.64%
common/types/mapper/thrift/shared.go	2	64.52%
service/history/execution/mutable_state_builder.go	2	69.77%
service/history/handler.go	2	48.32%
service/matching/matcher.go	2	91.46%
common/persistence/nosql/nosqlplugin/cassandra/workflow.go	3	55.49%
common/task/fifoTaskScheduler.go	3	82.47%

Totals
Change from base Build 4b4d4a8c-0384-4e44-b5a7-3adfc3216dee:	-0.04%
Covered Lines:	81009
Relevant Lines:	142914

---

💛 - Coveralls