Increase team-provisioner timeout to 300s

[Alexanderamiri]

Summary

• Increases team-provisioner Lambda timeout from 60s to 300s
• With 54 members, the Lambda timed out during group sync after creating all accounts
• Each member takes ~3s (check exists + create + forwarding attempt + welcome email), so 54 members alone need ~162s before group sync even starts

Context

The provision-groups run from registry PR #21 merge timed out at 60s. All accounts were created and welcome emails sent, but group membership sync didn't complete.

[github-actions]

Terraform Plan

🚧 Changes detected — Plan: 0 to add, 1 to change, 0 to destroy.

Plan output

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.lambdas.aws_lambda_function.team_provisioner will be updated in-place
  ~ resource "aws_lambda_function" "team_provisioner" {
        id                             = "javabin-team-provisioner"
        tags                           = {}
      ~ timeout                        = 60 -> 300
        # (22 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

---

LLM Review

Risk: 🟢 LOW

Routine Lambda timeout configuration update for team_provisioner function from 60 to 300 seconds.

• ✅ [routine] Lambda function timeout increased from 60 to 300 seconds - likely to accommodate longer provisioning operations
• ✅ [routine] Single in-place update with no resource destruction or replacement
• ✅ [routine] No security, IAM, or networking changes involved
• 💰 [cost] Potential minor cost increase due to longer Lambda execution time, but likely necessary for operational reliability