increase limit && change reading order to favor XMP

[qdraw]

PR Details

Description / Motivation and Context

This pull request introduces several changes to improve the handling of EXIF metadata, update the frontend component, and add new test data for long descriptions and titles. The most important changes include modifications to EXIF data reading functions, updates to the frontend's detail view sidebar, and the addition of new test data and corresponding test cases.

EXIF Data Handling Improvements:

• starsky/starsky.foundation.readmeta/ReadMetaHelpers/ReadMetaExif.cs: Updated the GetObjectName and GetCaptionAbstract methods to prioritize XMP data over IPTC data and ensure non-nullable return types.

Frontend Component Update:

• starsky/starsky/clientapp/src/components/organisms/detail-view-sidebar/detail-view-sidebar.tsx: Increased the maxlength attribute of the FormControl component from 1024 to 5000 to allow longer descriptions.

New Test Data and Test Cases:

• starsky/starskytest/FakeCreateAn/CreateAnImageLongDescriptionTitle/CreateAnImageLongDescriptionTitle.cs: Added a new class to handle long description and title test data.
• starsky/starskytest/FakeCreateAn/CreateAnImageLongDescriptionTitle/CreateAnImageLongDescriptionTitle.json: Added JSON file containing long description and title test data.
• starsky/starskytest/FakeCreateAn/CreateAnImageLongDescriptionTitle/CreateAnImageLongDescriptionTitleExampleDataModel.cs: Added a new data model class for long description and title test data.
• starsky/starskytest/starsky.foundation.readmeta/Services/ReadMeta_ExifReadTest.cs: Added a new test case to validate reading EXIF data from a file with long description and title.
• starsky/starskytest/starskytest.csproj: Updated the project file to include new test data files.

Related Issue

How Has This Been Tested

• C# Unit tests
• Typescript Unit tests
• Other Unit tests
• Manual tests
• Automatic End2end tests (starsky-tools/end2end)

Types of changes

• Added for new features
• Breaking change fix or feature that would cause existing functionality to change
• Changed for non-breaking changes in existing functionality for example docs change / refactoring / dependency upgrades
• Deprecated for soon-to-be removed features
• Removed for now removed features
• Fixed for any bug fixes
• Security in case of vulnerabilities

Checklist

• My code follows the code style of this project.
• I have updated the documentation accordingly (update when needed)
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated the ./history.md document

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud