support database creation from hiera parameters

[ikonia]

Summary

added $databases parameter to server.pp to allow iteration from server::database.pp to create databases
reusing the existing included pattern of $roles iterating through server::role.pp to manage roles

Additional Context

Add any additional context about the problem here.
Inability to create database using hiera parameters

Related Issues (if any)

new functionality but could also be considered a fix for #1620

Checklist

• [ x] 🟢 Spec tests.
• [ x] 🟢 Acceptance tests.
• [ x] Manually verified. (For example puppet apply)

[CLAassistant]

All committers have signed the CLA.

[ikonia]

tidied up git config on local machine to stop making commits with incorrect email account associated with GitHub account, merged in with correct email for CLA

[ikonia]

closed by accident

[ikonia]

the other merge requests that where grouped with this change (supporting grant creation, role creation) where merged into the last release, this one was excluded, which pretty much makes the other two pointless, as if you can't create the database, there is nothing to apply grants to

[jst-cyr]

CI test run for this PR: #1689

[jst-cyr]

@ikonia : Thank you for the extra context... I'm going to try to help this moving forward by getting acceptance tests running against a branch PR so we can get some feedback (if necessary) or at least mark as all green before the engineering review.

[jst-cyr]

@ikonia : It seems like testing is blocked right now because of a systemd mismatch on the metadata. There's already a PR submitted #1691 to resolve that so we can move testing forward.

[jst-cyr]

The metadata issue has been corrected and basic spec tests now pass green on this PR.
The acceptance test PR (#1689) was updated and the acceptance tests have been run. Results are here:

• https://github.com/puppetlabs/puppetlabs-postgresql/actions/runs/32032023426/job/95394491873?pr=1689

All 5 failing platforms in this PR's acceptance run (Scientific-7, OracleLinux-7, CentOS-7, Debian-13, SLES-12) match existing failures already happening in the nightly build against main. These aren't caused by your changes. Everything else in the matrix passed.

Compared PR run 32032023426 against nightly run 32032298372.

Next step is engineering review of the changes!

[ikonia]

if it makes things any easier/lighter work, if you review #1694 (comment) that already includes this change (as they are part of a set of changes needed to get full database lifecycle management working) or if you review this change, you've already reviewed part of the change included in #1694 (comment) depending on which way you look at it