Splitting wfCacheEnabled config for internal and external requests

[sankari165]

What changed?
WorkflowIDCacheEnabled config flag will be replaced by WorkflowIDCacheExternalEnabled and WorkflowIDCacheInternalEnabled

Why?
If the workflow cache is overwhelmed by one type of requests we can choose to enable/dsisable one of them without affecting the other

How did you test it?
unit tests

Potential risks
The cache is still not in use in production.

Release notes

Documentation Changes

[jakobht]

Looks good, but I think it's fine to just delete the WorkflowIDCacheEnabled in this PR?

[coveralls]

Pull Request Test Coverage Report for Build 018d8802-68d8-4158-9f88-2ca50acfa851

• 0 of 25 (100.0%) changed or added relevant lines in 3 files are covered.
• 77 unchanged lines in 15 files lost coverage.
• Overall coverage decreased (-0.002%) to 62.698%

---

Files with Coverage Reduction	New Missed Lines	%
common/task/weighted_round_robin_task_scheduler.go	1	89.05%
common/persistence/sql/sqlplugin/postgres/db.go	2	85.0%
common/persistence/sql/sqlplugin/postgres/task.go	2	73.4%
common/task/fifo_task_scheduler.go	2	85.57%
common/util.go	2	91.69%
service/frontend/api/handler.go	2	61.78%
service/history/shard/context.go	2	67.3%
service/matching/taskListManager.go	2	80.2%
common/persistence/nosql/nosqlplugin/cassandra/workflow.go	3	59.1%
common/persistence/statsComputer.go	3	94.29%

Totals
Change from base Build 018d8705-8ae5-4d48-8ec4-68c8df4537e5:	-0.002%
Covered Lines:	92247
Relevant Lines:	147128

---

💛 - Coveralls