[bitnami/postgresql-repmgr] Delay custom pg_hba.conf injection

[yukha-dw]

Description of the change

This container applies custom pg_hba.conf right before initialization process. This will cause an issue when we set security on pg_hba.conf. What this PR does is delaying custom pg_hba.conf injection until postgresql_initialize has been executed just like REPMGR_PGHBA_TRUST_ALL=no did to replace trust with md5 here:

containers/bitnami/postgresql-repmgr/16/debian-12/rootfs/opt/bitnami/scripts/librepmgr.sh

Lines 865 to 867 in 2de4377

	if ! repmgr_is_file_external "pg_hba.conf"; then
	is_boolean_yes "$REPMGR_PGHBA_TRUST_ALL" || postgresql_restrict_pghba
	fi

Benefits

Let user to customize pg_hba.conf without breaking initialization process, example:

hostnossl    all            all         all             reject
hostssl      repmgr         repmgr      all             scram-sha-256
hostssl      replication    repmgr      all             scram-sha-256
hostssl      all            repmgr      all             scram-sha-256
hostssl      all            all         all             scram-sha-256

Possible drawbacks

Other logic still able to break initialization process

Applicable issues

• fixes [bitnami/postgresql-repmgr] Cannot specify a custom pg_hba.conf #1048

Additional information

If we want to adapt this PR to bitnami/postgresql, I think we should refactor these lines:

containers/bitnami/postgresql/17/debian-12/rootfs/opt/bitnami/scripts/libpostgresql.sh

Lines 610 to 613 in 56c51a6

	if postgresql_is_file_external "pg_hba.conf"; then
	info "Custom configuration $POSTGRESQL_PGHBA_FILE detected"
	create_pghba_file=no
	fi

containers/bitnami/postgresql/17/debian-12/rootfs/opt/bitnami/scripts/postgresql/setup.sh

Lines 45 to 49 in 56c51a6

	# Remove any pg_hba.conf lines that match the given filters
	if ! postgresql_is_file_external "pg_hba.conf" && [[ -n "$POSTGRESQL_PGHBA_REMOVE_FILTERS" ]]; then
	info "Removing lines that match these filters: ${POSTGRESQL_PGHBA_REMOVE_FILTERS}"
	postgresql_remove_pghba_lines
	fi

[migruiz4]

I'm sorry for the late response @yukha-dw, could you please take a look at my comments?