Fix CI failing due to linter/style errors

[Copilot]

This PR resolves the CI failures caused by linter and style configuration issues in the codebase.

Changes Made

1. Fixed TypeScript Type Naming Convention

• Renamed the type alias Object_ to ObjectType in index.d.ts
• The previous name Object_ violated the StrictPascalCase naming convention required by XO's TypeScript rules
• ObjectType follows proper TypeScript naming conventions and is more descriptive

2. Fixed JavaScript Formatting Issues

• Resolved newline formatting issues in index.js using XO's auto-fix functionality
• Removed unexpected newlines after ( and before ) in function calls/declarations

3. Updated Linter Configuration

• Replaced the ineffective eslintIgnore configuration with proper XO ignore patterns
• Added xo.ignores configuration in package.json to ignore all *.d.ts files from linting checks
• This prevents future TypeScript definition files from being linted with JavaScript/TypeScript style rules

Before vs After

Before:

type Object_ = Record<string, unknown>;  // ❌ Violated naming convention

After:

type ObjectType = Record<string, unknown>;  // ✅ Follows StrictPascalCase

Configuration:

// Before (ineffective)
"eslintIgnore": ["index.d.ts"]

// After (works with XO)
"xo": {
  "ignores": ["*.d.ts"]
}

Verification

• ✅ All tests pass (npm test)
• ✅ Linting passes without errors (npm run lint)
• ✅ XO properly ignores TypeScript definition files
• ✅ CI should now pass without linter/style errors

Fixes #71.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

@palashmon 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.