fix: fix bug in generateNewIdentifierByStoredProcedure

[vera]

What this PR does / why we need it:

This fixes a bug which prevents PIDs being generated using the db function generateIdentifierFromStoredProcedure. For more details see the issue below.

Which issue(s) this PR closes:

• Closes ERROR: procedure generateidentifierfromstoredprocedure(unknown) does not exist #12126

Special notes for your reviewer:

/

Suggestions on how to test this:

• Start Dataverse configured with a default PID provider with identifier-generation-style=storedProcGenerated, e.g.

        -Ddataverse.pid.testpid.type=perma
        -Ddataverse.pid.testpid.label=PermalinkProvider
        -Ddataverse.pid.testpid.authority=test
        -Ddataverse.pid.testpid.shoulder=
        -Ddataverse.pid.testpid.permalink.base-url=https://example.com/
        -Ddataverse.pid.testpid.permalink.separator=-
        -Ddataverse.pid.testpid.identifier-generation-style=storedProcGenerated

• Create function in the db, e.g. using one of the examples here https://guides.dataverse.org/en/latest/installation/config.html#dataverse-pid-identifier-generation-style
• Create a dataset
• Check that the dataset is successfully created and received a generated identifier according to the configured db function

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

/

Is there a release notes update needed for this change?:

Not sure

Additional documentation:

/

[qqmyers]

This looks like the analogous change we made to the download estimation query, so I'll approve it. @vera - thanks for the quick fix - can you add a release note so we make sure that people know this is fixed (in 6.10 at least).

[vera]

can you add a release note so we make sure that people know this is fixed (in 6.10 at least).

Done!