Bump version and update package name

[Arctis-Fireblight]

Summary by CodeRabbit

• Chores
  • Version updated to 2.5.3
  • Product rebranded as "Simple Calendar Reborn"

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Package and module version incremented from 2.5.2 to 2.5.3 across configuration files. Module title updated to "Simple Calendar Reborn" in module metadata.

Changes

Cohort / File(s)	Summary
Configuration and metadata updates package.json, src/module.json	Version bumped from 2.5.2 to 2.5.3 in package.json. Module metadata updated: title changed to "Simple Calendar Reborn" and version incremented to 2.5.3 in src/module.json.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: bumping the version from 2.5.2 to 2.5.3 and updating the module name from 'Simple Calendar' to 'Simple Calendar Reborn'.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3867f99 and 55ef6d9.

📒 Files selected for processing (2)

• package.json
• src/module.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (3)

package.json (1)

4-4: LGTM!

The version bump from 2.5.2 to 2.5.3 follows semantic versioning for a patch release.

src/module.json (2)

3-3: LGTM!

The title update to "Simple Calendar Reborn" aligns with the rebranding effort and is consistent with the package name.

---

5-5: Verify the version format change from 4-segment to 3-segment.

The version changed from "2.5.2.0" (4-segment) to "2.5.3" (3-segment). While FoundryVTT typically uses semantic versioning (3-segment), ensure this format change was intentional and won't cause issues with version comparison logic or update mechanisms in FoundryVTT.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}