Reapply updated Copier templates and streamline developer workflow

[AndrewSazonov]

This PR reapplies the latest EasyScience Copier templates to align the repository with updated project structure, CI workflows, and configuration.

As part of this maintenance work, pre-commit and pre-push hooks are temporarily disabled to simplify local development. Instead, developers are expected to:

• run pixi check to manually run code quality checks and unit tests (at least before opening a PR),
• run pixi fix to apply all automatic formatting and lint fixes.

This keeps the workflow lightweight during active development while preserving consistent quality checks.

To ensure these checks are not forgotten, the Code quality checks workflow is still executed on every push and pull request, so any remaining issues must be addressed before merging.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (develop@88af3d9). Learn more about missing BASE report.

Additional details and impacted files

@@            Coverage Diff             @@
##             develop      #97   +/-   ##
==========================================
  Coverage           ?   97.91%           
==========================================
  Files              ?       32           
  Lines              ?     1825           
  Branches           ?      296           
==========================================
  Hits               ?     1787           
  Misses             ?       21           
  Partials           ?       17           

Flag	Coverage Δ
integration	0.00% <ø> (?)
unittests	97.91% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[henrikjacobsenfys]

LGTM

I may want to get rid of some icons in the readme and docs since they're overused by AI and may therefore send the wrong signal to users. But that's for general cleanup which will be later

[AndrewSazonov]

I understand the concern. Just to clarify, these are standard Unicode icons that are supported everywhere. The main idea is to make the lists easier to read and quicker to recognize visually.

For now, I wouldn’t suggest changing the README. The current version is auto-generated as a minimal and clean README, with the most important links and a consistent visual style across all EasyScience projects. This is based on the project configuration in the home repository (in this case easyscience/dynamics).

Later, when this becomes an ADR suggestion, I’d be happy to collect feedback and discuss things like icon usage there, so we can make a common decision for the whole organization instead of changing things project by project 🙂

[henrikjacobsenfys]

I understand the concern. Just to clarify, these are standard Unicode icons that are supported everywhere. The main idea is to make the lists easier to read and quicker to recognize visually.

For now, I wouldn’t suggest changing the README. The current version is auto-generated as a minimal and clean README, with the most important links and a consistent visual style across all EasyScience projects. This is based on the project configuration in the home repository (in this case easyscience/dynamics).

Later, when this becomes an ADR suggestion, I’d be happy to collect feedback and discuss things like icon usage there, so we can make a common decision for the whole organization instead of changing things project by project 🙂

Yeah, let's discuss such details it when the ADR suggestion is there. It's so much better than what I had, and the consistency between projects is really nice.