do not calculate classpath-cache on require

[thumbnail]

Brief

This is reported to cause a lot of io, which could cause timeouts when when booting. By putting this into a delay the classpath-cache is calculated on the first kondo linter run.

QA plan

1. release alpha
2. remove .clj-kondo-folder from projects known to cause this issue
3. boot repl; observe no timeout
4. run f-s; observe creation of cache
5. run f-s again; observe faster run

Author checklist

• [ ] I have QAed the functionality
• [ ] The PR has a reasonably reviewable size and a meaningful commit history
• [ ] I have run the branch formatter and observed no new/significative warnings
• [ ] The build passes
• [ ] I have self-reviewed the PR prior to assignment
• Additionally, I have code-reviewed iteratively the PR considering the following aspects in isolation:
  • [ ] Correctness
  • [ ] Robustness (red paths, failure handling etc)
  • [ ] Test coverage
  • [ ] Spec coverage
  • [ ] Documentation
  • [ ] Security
  • [ ] Performance
  • [ ] Breaking API changes
  • [ ] Cross-compatibility (Clojure/ClojureScript)

Reviewer checklist

• [ ] I have checked out this branch and reviewed it locally, running it
• [ ] I have QAed the functionality
• [ ] I have reviewed the PR
• Additionally, I have code-reviewed iteratively the PR considering the following aspects in isolation:
  • [ ] Correctness
  • [ ] Robustness (red paths, failure handling etc)
  • [ ] Test coverage
  • [ ] Spec coverage
  • [ ] Documentation
  • [ ] Security
  • [ ] Performance
  • [ ] Breaking API changes
  • [ ] Cross-compatibility (Clojure/ClojureScript)

[thumbnail]

mitigated by not loading f-s when the repl is loaded. instead we create aliases which use requiring-resolve to load f-s upon first reload / format.