Introducing sort-issues-by option

[suyashgaonkar]

Description:
Introducing a new option sort-issues-by to sort the issues by the specified field. It accepts 'created', 'updated', 'comments' as values and default value is set to 'created', defines the sorting order of the issues in a repository.

Related issue:
Related to #1231

Check list:

• [✓ ] Mark if documentation changes are required.

[Copilot]

Pull Request Overview

Adds a new sort-issues-by option so users can control how issues are ordered (by creation date, last update, or comment count).

• Parses sort-issues-by input and wires it through the options interface.
• Registers the option in the enum and action metadata.
• Implements sort logic in the GitHub API call and provides defaults in tests.

Reviewed Changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/main.ts	Parse sort-issues-by from action inputs
src/interfaces/issues-processor-options.ts	Add sortIssuesBy property to options interface
src/enums/option.ts	Add SortIssuesBy enum entry
src/classes/issues-processor.ts	Use sortIssuesBy to set the API sort parameter
src/classes/issue.spec.ts	Initialize default sortIssuesBy in tests
action.yml	Declare the new sort-issues-by input
tests/constants/default-processor-options.ts	Include default sortIssuesBy in defaults

Comments suppressed due to low confidence (1)

src/classes/issues-processor.ts:574

• There are no tests verifying how different sortIssuesBy values (updated, comments) affect the API request. Add unit tests to ensure each option sends the correct sort parameter.

sort: