Refactor enrollments route to include query building

Changes:

• Add error handling in the database query function. When a database error occurs, it is logged in the server and a plain text response is returned to the user.
• Implement building of SQL queries inside the API, which removes the need to have stored functions/procedures on the database, since the former approach is not flexible or efficient to maintain/extend.
• Use route chaining to determine which function will build the query that needs to be executed. The last function is the one that actually sends the query to the database and send the response.

Future Work:

• Instead of returning a plain text response, return a HTTP 501 status, which is currently not possible. When one attempts to send such status the framework throws an error that the headers were already sent for the current request.
• Chaining based on the route might not be the best solution here.

src/libs/routes/city.js

@@ -3,7 +3,6 @@ const cityApp = express();
 const libs = `${process.cwd()}/libs`;
 const log = require(`${libs}/log`)(module);
 const squel = require('squel');
-const dbQuery = require(`${libs}/db/query_exec`);
 const query = require(`${libs}/middlewares/query`);
 const response = require(`${libs}/middlewares/response`);
 
@@ -19,8 +18,6 @@ cityApp.get('/:id', (req, res, next) => {
 }, query, response);
 
 cityApp.get('/ibge/:id', (req, res, next) => {
-    const citySql = 'SELECT * FROM municipios WHERE codigo_ibge = ?';
-    const cityIbgeCode = req.params.id;
     req.query = squel.select().from('municipios').where('codigo_ibge = ?',
         parseInt(req.params.id, 10)).toParam();
     next();