Bastion updates

@here we have some update for our bastions pipeline using jenkins.

We've created two bastions that will be used from jenkins.

1. dynamic-bastion (this is done) :heavy_check_mark:
pipeline : https://deploy.tvlk-pay.com/job/dynamicbastion/

This dynamic bastion featured dual-custody process to spawn the instance for other person in the team.

Team leaders have access to run the bastion for their team members
Team member that has access the bastion is the only person who can connect the instance with public key with the time already specified
Team leaders cannot give access to themselves

2. bastion db executor (Work in progress) :negative_squared_cross_mark:
pipeline: https://deploy.tvlk-pay.com/job/bastion-db-executor-test/ (WIP) cc @Ican @amal.syahreza

This pipeline will spawn bastion instance to run a specific scripts. No dual-custody required, and bastion will run the script from the instance that can access databases.
For parameters on this pipeline, we still work from backend and the logic.

Here's some other things for heads-up

We will testing the pipeline on the staging environment first, @Ican is still helping us from this
The parameters on this pipeline is not final, will be change if necessary
Will the bastion targeting the primary or read replica (?)
Are we will be using a different pipelines to separate the scripts type (sql, curl, nodejs-script) (?)
How we will separate between read-only queries vs write/update queries (?)

kindly need your feedback for what we want to achieve here