feat(recovery): add crash recovery implementation

[Yogesh01000100]

This PR addresses issue #3114

Changes

• Crash Recovery: Updated crash_recovery.proto and related ts files; added core recovery logic (created functions not yet implemented).
• Knex Config: Improved knexfile.ts and knexfile-remote.ts; added Docker Compose for production.

[RafaelAPB]

I will review this PR

[RafaelAPB]

@Yogesh01000100 please rebase with satp-dev (should not have conflicts)

[RafaelAPB]

@Yogesh01000100 please include documentation and tests, and update the description, as discussed.

[RafaelAPB]

@Yogesh01000100 could you please squash the commits and rebase with latest version of satp-dev, prior to merge?

[RafaelAPB]

Generally looks very good, but there are some changes to be done prior to merging.
Summarizing my comments:

1. Add other authors to the commit
2. Incorporate feedback from the logging process (namely un-hardcoding logs and adding more information)
3. Implement RollbackState (for example, should state how many more steps are to be rolled-back, at any moment; what was rolledback already; estimated time to completion, etc)
4. Please add tests that support the new feature
5. Please add comprehensive documentation on this feature. Example: The readme of SATP should have a section on how to run the docker compose with several examples of configurations.

[RafaelAPB]

We will need to do a few changes. We will have a satp runner image that encapsulates satp. The docker file is being developed by Bruno (please sync with him). In particular, please note what are the necessary env variables that need to be fed to docker compose.

See suggestion below:

version: '3.8'

services:
  db:
    image: postgres:13
    environment:
      POSTGRES_DB: ${DB_NAME}
      POSTGRES_USER: ${DB_USER}
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_HOST: ${DB_HOST}
      PGPORT: ${DB_PORT}
    ports:
      - "${DB_PORT}:5432"
    volumes:
      - pgdata:/var/lib/postgresql/data

  satp-runner:
    image: satp-runner-gateway:latest  #to be published
    environment:
      # environment variables your SATP runner needs
    ports:
      - "3000:3000"  #  port mapping
    depends_on:
      - db

volumes:
  pgdata:

Additionally, we will need a load balancer, and other services for monitoring (@eduv09 will implement those). We would have something like this:

  nginx:
    image: nginx:latest
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf:ro
    ports:
      - "80:80"
    depends_on:
      - satp-runner

  prometheus:
    image: prom/prometheus:latest
    volumes:
      - ./prometheus.yml:/etc/prometheus/prometheus.yml
      - prometheus_data:/prometheus
    command:
      - '--config.file=/etc/prometheus/prometheus.yml'
      - '--storage.tsdb.path=/prometheus'
      - '--web.console.libraries=/usr/share/prometheus/console_libraries'
      - '--web.console.templates=/usr/share/prometheus/consoles'
    ports:
      - "9090:9090"

  grafana:
    image: grafana/grafana:latest
    volumes:
      - grafana_data:/var/lib/grafana
    environment:
      - GF_SECURITY_ADMIN_USER=${GRAFANA_ADMIN_USER:-admin}
      - GF_SECURITY_ADMIN_PASSWORD=${GRAFANA_ADMIN_PASSWORD:-admin}
    ports:
      - "3000:3000"
    depends_on:
      - prometheus

[RafaelAPB]

I did many contributions to this code. Unfortunately the squash you did removed that history.

Please add me as a co-author to the squashed commit:
https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors

[RafaelAPB]

Why is this commented?

[RafaelAPB]

Why is this commented?

[RafaelAPB]

Same

[RafaelAPB]

Please remove todos when the task is completed. I see you are already recording the rollback log entry (despite being a dummy entry). Please un-hardcode it, and gather information from the current session

[RafaelAPB]

Please un-hardcode the log creation where applicable

[RafaelAPB]

Please un-hardcode the log creation where applicable.
For instance, details can be a subset of the execution trace to the moment. Remember, these logs should help developers finding bugs or understanding the state of the application at any moment

[RafaelAPB]

Please see comments from other stages

[RafaelAPB]

Let us please fix the latest working version of the generator in package.json (if not done yet)