Fix compliance findings in Frends.IbmMaximo.Request (v1.2.0)

[Copilot]

Resolves task scanner compliance findings: missing csproj metadata, net6.0 target, absent Options parameter on the main task method, and missing <example> XML doc tags.

csproj

• Added <Company>Frends</Company> and <Product>Frends</Product>
• Changed <PackageProjectUrl> to https://frends.com/
• Upgraded target framework: net6.0 → net8.0
• Bumped version 1.1.0 → 1.2.0

New Options parameter (FT0007)

Added Options class and wired it into the main Request entry point:

public static async Task<Result> Request(
    [PropertyTab] Input input,
    [PropertyTab] Options options,   // new
    CancellationToken cancellationToken)

Options exposes ThrowErrorOnFailure (default true) and ErrorMessageOnFailure. The method now wraps dispatch in a try/catch that either rethrows or returns Result(Success=false) based on those settings. Sub-methods (CreateWorkOrder, CustomRequest, etc.) are unchanged.

XML documentation (FT0014)

Added <example> tags to the 13 Input properties that were missing them (RequestType, WorkOrderDescription, ServiceRequestDescription, ReportedBy, WorkOrderLocation, ServiceRequestLocation, WorkOrderAssetNum, ServiceRequestAssetNum, Site, ScheduledStart, ReportedDate, WorkOrderId, ServiceRequestId).

[jefim]

@copilot address the review comments

[jefim]

Adding a new Options parameter to the task signature is a breaking change

[Copilot]

Correct — bumped to 2.0.0 in the csproj and CHANGELOG. Fixed in commit $(git rev-parse --short HEAD).