[tools] Add command to close Linear issues given a GitHub issue (#22205)

# Why

To further improve our issue management, it would be ideal to
automatically close Linear issues whenever a Github i

[tools] Add command to close Linear issues given a GitHub issue (#22205)

# Why

To further improve our issue management, it would be ideal to
automatically close Linear issues whenever a Github issue we've imported
is closed.

# How

This PR introduces a new et command to mark a Linear issue as Done and
comment on the Linear ticket linking the GitHub PR that closed the
issue. This also adds a new GitHub workflow that automatically triggers
this command when an issue with the `Issue accepted` is closed.

# Test Plan

run `et clifg -i XXXX` locally




# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[tools] Update Linear getTeamMembersAsync to not throw when no results are found (#22095)

# Why

The `issue-accepted` workflow is failing to run `et igitl` when a user
that does not have an accou

[tools] Update Linear getTeamMembersAsync to not throw when no results are found (#22095)

# Why

The `issue-accepted` workflow is failing to run `et igitl` when a user
that does not have an account on Linear is assigned to the GitHub issue

E.g.
https://github.com/expo/expo/actions/runs/4672005201/jobs/8273691721

# How

Instead of throwing an error when no team members have been found we
just return an empty array

# Test Plan

Run `et igitl --issue 22024` locally

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[tools] Add command to import accepted issues from GitHub to Linear (#22062)

# Why

In order to facilitate the management of SDK issues this PR proposes
automatically importing GitHub issues labe

[tools] Add command to import accepted issues from GitHub to Linear (#22062)

# Why

In order to facilitate the management of SDK issues this PR proposes
automatically importing GitHub issues labeled with the `issue-accepted`
tag to Linear, allowing us to better keep track of the status of each
individual issue, adding them to SDK projects, and centralizing internal
discussions in a single place.

Closes ENG-8130

# How

This PR introduces a new `et` command to import accepted issues from
GitHub to Linear, `et import-github-issue-to-linear` and also updates
the `issue-accepted` job of the `Issue Triage` workflow to run it every
time an issue is labeled as accepted.

To make the issue summary more concise and readable, this new command
uses GPT-4 to automatically summarize the problem described in the
GitHub issue, allowing team members to quickly skim through the text and
understand the issue.

Additionally, this new command attempts to infer a Linear user to assign
the issue by checking for users with the same full name, nickname, or
email address, in case a user was added as an assignee in the GitHub
issue.

Example of an issue automatically imported -> ENG-8187

# Test Plan

Run `et igitl --issue X` locally

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...