Explicit taskHub parameter for stored procedures

Please consider changing approach from using implicit dt.CurrentTaskHub() to explicit parameter in all procedures.

Rational. Flexibility in support database sharing/isolation approaches and simplicity.

For example, from documentation: "This is often valuable when your organization has many small apps but prefers to manage only a single backend database. When multitenancy is enabled, different apps connect to a shared database using different database login credentials and each app will only have access to its own data." Explicit assumption of different login is not flexible, and might be not reflecting reality for majority of financial organizations that actually want to share the database schema.

Start by reviewing the stored procedures and the uses of implicit dt.CurrentTaskHub() referenced in the issue, then compare them with the multitenancy documentation example. The issue does not name files or tests; completion would require an agreed explicit-parameter design, updates across the affected procedures, and corresponding documentation changes.