Enhance backup::restore function to support PostgreSQL in addition to RocksDB

[msk]

Description

Currently, the backup::restore function is designed to restore backups for RocksDB only. This issue aims to enhance this function to support PostgreSQL as well.

This change would involve not only restoring the state of the RocksDB store but also the PostgreSQL database from its corresponding backup. It's proposed to use psql command for restoring the PostgreSQL backup.

Tasks

1. Modify the backup::restore function to restore both RocksDB and PostgreSQL databases.
2. Ensure the function identifies the correct backup files for each database type.
3. Use the psql command to restore the PostgreSQL backup.
4. Thoroughly test the new functionality, ensuring that it can correctly restore the state of both the RocksDB store and the PostgreSQL database.

Acceptance Criteria

1. The backup::restore function is able to restore both RocksDB and PostgreSQL backups.
2. All tests pass without causing any regression.

[kimhanbeom]

@msk @syncpark

I am currently working on an implementation, referring to the restoration part of https://github.com/aicers/cli.
In order to use this feature, I need to call sudo_run_command and that requires root privileges.

To solve this, it looks like we need to choose one of 2 ways.

1. Run review as root to perform the command.
2. Add sudo_run_command to roxy to perform the command via roxy.

[msk]

Which step requires the root privilege?

[kimhanbeom]

The part of the postgres_restore_docker function that moves data from the existing postgresql to tmp requires permissions.

[msk]

Could we consider the option of creating a temporary directory that's writable for the REview process instead? This way, we can circumvent the need for superuser permissions during the process of moving data from existing postgresql to a temporary directory.

It's generally a bad practice to run applications with root privileges unless absolutely necessary, due to the significant security risks involved. When a process runs with root privileges, it has unrestricted access to the system. This means it can read, write, and delete every file on your system, and it can execute any command. If any vulnerabilities exist within the application, an attacker could exploit them to gain full control over the system.