Fix a TS error when using Inngest in projects with composite setting (

#460)

## Summary
<!-- Succinctly describe your change, providing context, what you've
changed, and why. -->
This PR Adds some type exports to `index.ts` that fix a TS error in
composite projects.

After changes to the `types.ts` the issue #384 appeared again. This PR
is similar to #385 - it fixes the TS error by adding necessary exports
to the `index.ts`

## Checklist


- [ ] ~~Added a [docs PR](https://github.com/inngest/website) that
references this PR~~ N/A no docs needed
- [ ] ~~Added unit/integration tests~~ N/A not testable
- [x] Added changesets if applicable

## Related
- #385 
- #384

---------

Co-authored-by: Jack Williams <1736957+jpwilliams@users.noreply.github.com>

.changeset/tall-hornets-beg.md

@@ -0,0 +1,5 @@
+---
+"inngest": patch
+---
+
+Add exports for `FinishedEventPayload` and `Context` types to fix a TypeScript error when using Inngest in projects with `composite` setting in `tsconfig`.

packages/inngest/src/index.ts

@@ -38,10 +38,12 @@ export { ProxyLogger } from "./middleware/logger";
 export type { LogArg } from "./middleware/logger";
 export type {
   ClientOptions,
+  Context,
   EventNameFromTrigger,
   EventPayload,
   FailureEventArgs,
   FailureEventPayload,
+  FinishedEventPayload,
   FunctionOptions,
   FunctionTrigger,
   Handler,

packages/inngest/src/types.ts

@@ -99,6 +99,12 @@ export type FailureEventArgs<P extends EventPayload = EventPayload> = {
   error: Error;
 };
 
+/**
+ * The payload for an internal Inngest event that is sent when a function
+ * finishes, either by completing successfully or failing.
+ *
+ * @public
+ */
 export type FinishedEventPayload = {
   name: `${internalEvents.FunctionFinished}`;
   data: {
@@ -278,6 +284,8 @@ export type BaseContext<
 /**
  * Builds a context object for an Inngest handler, optionally overriding some
  * keys.
+ *
+ * @internal
  */
 export type Context<
   TOpts extends ClientOptions,