FedEx pickup: tighten option enum declarations and centralize strict validation

[Chris Nolan.ca (ChrisNolan)]

Background

In the FedEx pickup flow, several options are declared as plain OptionEnum string values instead of typed enum options:

• modules/connectors/fedex/karrio/providers/fedex/pickup/create.py
• modules/connectors/fedex/karrio/providers/fedex/pickup/update.py

We recently added ( #1112 ) strict validation helpers for pickup fields:

• modules/connectors/fedex/karrio/providers/fedex/pickup/utils.py

Problem

Current option declarations do not consistently express carrier-allowed values at declaration time, which makes behavior less explicit and spreads validation logic across request builders.

Proposal

• Introduce FedEx pickup-specific typed enums for option fields such as:
  • carrierCode
  • pickupDateType
  • pickupAddressType
• Update pickup option declarations to use OptionEnum with typed enums and defaults where applicable.
• Keep strict validation for closed sets where unknown values must hard-fail.
• Normalize values to expected FedEx casing before request serialization.

Acceptance Criteria

• FedEx pickup option declarations are typed and self-documenting.
• pickupAddressType defaults to OTHER when omitted.
• Invalid pickupAddressType and packageLocation fail before outbound API calls.
• Existing FedEx pickup behavior and tests remain green.
• Unit tests explicitly cover:
  • valid enum values
  • omitted values using defaults
  • invalid values raising FieldError

Test Plan

• Run:
  • source bin/activate-env
  • python -m unittest discover -v -f modules/connectors/fedex/tests
• Ensure pickup test coverage includes positive/default/negative enum cases in:
  • modules/connectors/fedex/tests/fedex/test_pickup.py