feat: add Glossary Entry suggestion status

[andreyfurdylo]

Replace this text with a description of your proposed change.

JOBS-8469

Add Glossary Entry suggestion status

Squash Commit Guidelines

This is a reminder on how to format your sqaush commit message. Delete from your PR after noting below.

Message Header

The message header is a single line that contains succinct description of the change containing a type: subject. For example:

feat: add Foo API

Allowed Types

This describes the kind of change that this commit is providing:

• feat (when adding feature)
• fix (when performing a bug fix)
• docs (when adding or changing documentation)
• refactor (when doing non-breaking code refactoring)
• test (when adding missing tests)
• chore (when performing maintainance)

Subject Text

This is a very short description of the change.

• use imperative, present tense: “change” not “changed” nor “changes”
• no dot (.) at the end

[Copilot]

Pull Request Overview

This PR adds a new suggestionStatus field to glossary entries, allowing tracking of whether entries are "SUGGESTED" or "APPROVED". This enhancement supports the workflow for managing glossary entry suggestions in the Smartling platform.

• Added suggestionStatus field to the GlossaryEntryBaseResponsePTO class
• Updated test data to include the new field in JSON response
• Added test assertion to verify the field is properly parsed

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
GlossaryEntryBaseResponsePTO.java	Added suggestionStatus field with documentation
EntryManagementApiTest.java	Updated test data and assertions to include suggestionStatus field