Adding an API endpoint to manage Keyword Policy filters

As per !794 (merged), Keyword Policy data is stored in config.exs. While it is currently the default location for such settings, having an API endpoint to manage this data from the front-end might be a nice thing to have

Roadmap

Currently, I am planning to

• Add management API routes
• Handle Keyword Policy data retrieval
• Save this data in application environment

Related issues

• Storing the MRF Policies on database : #644 (closed)