Update Azure Files docs for connector 1.0.1 and drop version pins

[YasanPunch]

Follow-up to #617, syncing the merged Azure Files docs to ballerinax/azure.storage.files 1.0.1, plus a small convention change.

1.0.1 sync

• RetryPolicyType.FIXED → FIXED_INTERVAL — renamed in 1.0.1. The configuration value stays "fixed", so only the enum member name changes. LeaseDuration.FIXED is a different enum and is deliberately left alone.
• Catalog card icon — added, now that the package is published on Ballerina Central. The card was falling back to a letter tile because icon was omitted back when 1.0.0 was unpublished.
• Handler panics — the trigger reference's afterError row now says "returns an error or panics", matching both the 1.0.1 behaviour fix and the wording already in the file-integration guide.

Version pins dropped (Azure Files + FTP)

Rather than bump the Azure Files overview to v1.0.1, the pin is removed. A pinned version goes stale on the next release with nothing to update it — this page was stale within two days of publishing — and readers get the current version from Ballerina Central, which the catalog card already links to. FTP's (v2.19.0) pin is removed for the same reason, as the other file-integration page our team owns that carries one.

The card icon URL keeps its version deliberately: Central's icon CDN requires one in the filename (the versionless URL 404s) and old URLs keep serving, so a pinned icon is invisible to readers.

The remaining pinned pages across the catalog belong to other teams and are tracked in wso2-enterprise/integration-engineering#2751.

The restored onFileCsv string row forms, the other notable 1.0.1 change, were already documented in #632.

Verified by compiling the documented samples against 1.0.1 resolved from Ballerina Central, including files:FIXED_INTERVAL. Site build is clean apart from two pre-existing 5.1.x warnings unrelated to these pages.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: bf2ee644-6026-465c-97ca-6030d164a06e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}