Deps: Upgrade to Ionic 7.6 and use Ionic Standalone components

[rsreimer]

Which issue does this PR close?

This PR closes #3342

What is the new behavior?

Does this PR introduce a breaking change?

• [ ] Yes
• [x] No

Are there any additional context?

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Reminders

• [x] Make sure you have implemented tests following the guidelines in: "The good: Test".
• [x] Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).

Review

• [x] Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
• [x] Do a self-review.
• [x] Request that the changes are code-reviewed
• [ ] Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)

When the pull request has been approved it will be merged to develop by Team Kirby.

[RasmusKjeldgaard]

One nice addition to this PR would be to export something like the following from e.g. our /shared/ entry.

export const provideKirby = (): Provider[] => {
  // config object is defined in kirby-ionic-module, should probably be moved to a shared location
  return provideIonicAngular(config);
};

Then Standalone-based applications should be able to use Kirby out of the box:

bootstrapApplication(AppComponent, {
  providers: [provideKirby()],
}).catch((err) => console.error(err));