SetSealImageAsset() is ignored by .NET SDK (v4.3.1)

# Bug Report: `SetSealImageAsset()` is ignored by .NET SDK (v4.3.1)

## Summary

When using the .NET SDK (`Adobe.PDFServicesSDK` v4.3.1) to create an Electronic Seal, the custom seal image provided via `SetSealImageAsset()` is not rendered in the resulting PDF.

The exact same workflow and assets work correctly when submitting the Electronic Seal job through the REST API using `sealImageAssetID`.

This suggests that the issue is related to the SDK submit implementation rather than the backend service or the uploaded assets.

---

## Environment

- SDK: `Adobe.PDFServicesSDK` **4.3.1**
- .NET: (please insert your version)
- Authentication: Service Principal
- CSC Provider: Intesi
- Credential Type: CSC
- Signature: Electronic Seal

---

## Expected Behavior

The custom seal image supplied through:

```csharp
pdfElectronicSealJob.SetSealImageAsset(sealImageAsset);
```

should be rendered as part of the visible electronic seal.

---

## Actual Behavior

The PDF is sealed successfully.

The visible seal is rendered, however the custom seal image is ignored and only the default appearance is shown.

---

## What was verified

The following have been verified:

- ✅ PDF is successfully sealed.
- ✅ CSC authentication works correctly.
- ✅ Intesi access token is valid.
- ✅ Input PDF uploads successfully.
- ✅ Seal image uploads successfully.
- ✅ `AppearanceOptions` contains `AppearanceItem.SEAL_IMAGE`.
- ✅ `SetSealImageAsset()` is called before submitting the job.
- ✅ JPEG, PNG and PDF seal images were tested.
- ✅ Different image sizes were tested.
- ✅ Different signature field sizes and locations were tested.

---

## Important Finding

I implemented the exact same workflow using the REST API.

The only difference is that instead of:

```csharp
pdfElectronicSealJob.SetSealImageAsset(sealImageAsset);
```

the REST request contains:

```json
{
"sealImageAssetID": ""
}
```

The REST implementation renders the custom seal image correctly.

The uploaded asset IDs are identical to those uploaded through the SDK.

---

## Comparison

| Step | SDK | REST |
|------|-----|------|
| Upload PDF asset | ✅ | ✅ |
| Upload seal image asset | ✅ | ✅ |
| CSC authentication | ✅ | ✅ |
| Submit Electronic Seal job | ✅ | ✅ |
| Seal image rendered | ❌ | ✅ |

---

## Sample SDK code

```csharp
AppearanceOptions appearanceOptions = new AppearanceOptions();
appearanceOptions.AddItem(AppearanceItem.NAME);
appearanceOptions.AddItem(AppearanceItem.LABELS);
appearanceOptions.AddItem(AppearanceItem.DATE);
appearanceOptions.AddItem(AppearanceItem.SEAL_IMAGE);
appearanceOptions.AddItem(AppearanceItem.DISTINGUISHED_NAME);

PDFElectronicSealParams parameters =
PDFElectronicSealParams.PDFElectronicSealParamsBuilder(
certificateCredentials,
fieldOptions)
.WithAppearanceOptions(appearanceOptions)
.Build();

PDFElectronicSealJob job = new PDFElectronicSealJob(asset, parameters);

job.SetSealImageAsset(sealImageAsset);

string location = pdfServices.Submit(job);
```

---

## Working REST payload

```json
{
"inputDocumentAssetID": "...",
"sealImageAssetID": "...",
"sealOptions": {
"sealAppearanceOptions": {
"displayOptions": [
"NAME",
"LABELS",
"DATE",
"SEAL_IMAGE",
"DISTINGUISHED_NAME"
]
}
}
}
```

This renders the custom seal image correctly.

---

## Conclusion

Since:

- the same uploaded assets are used,
- the same CSC credentials are used,
- the same provider is used,
- the same appearance options are used,

and only the SDK implementation fails to render the seal image, while the REST API works correctly,

it appears that the .NET SDK is not submitting the seal image correctly (or is generating a different request than the REST API).

Could you please verify whether `SetSealImageAsset()` is correctly serialized into the request sent by the .NET SDK?

If needed, I can also provide:

- sample input PDF
- sample seal image
- working REST implementation
- non-working SDK implementation
- transaction IDs

.NET SDK が送信したリクエストと、動作する REST ペイロードを比較することから始め、SetSealImageAsset() がどのようにシリアライズされるかに注目してください。リクエストに sealImageAssetID が含まれていることを確認し、生成された PDF にカスタムの印影画像がレンダリングされたら完了を確認してください。

索引モデルが issue の本文から書いたものです。