Semantic routing to process advisor stage

[mhgov]

UF: Standardise process Do exploration with client first to dig out all information, listen to client

Solution: Caddy currently assumes exploration with client has occured, some advisros starting from 1st level query. two fold - train advisors so clear on what cddy is expecting, second look at sematnic routing

use 1st stage reword to understand whether the output has asked question, v.s. client query etc. Use this to move between various prompt routing

Split core prompt in the dynamo db table. potentially also reword/process dependent on chat clietn (gchat v.s. teams)