Modify the logic to validate the size comparison between the token's expiration time and refresh frequency so that it is executed only in init mode

[y-myajima]

Description

We have modified the system so that when starting in init mode, it no longer performs a size comparison between the TokenRefresh and TokenExpiry settings at startup.

• The size comparison between TokenRefresh and TokenExpiry is a logic used to prevent the token from expiring before the cache is updated when starting in refresh mode. Therefore, it is not necessary to execute the above comparison and validation logic in init mode.

Assignees

• Assignees is set

Type of changes

• Apply one or more labels of the following that fits:
  • bug: Bug fix
  • dependencies: Dependency upgrades
  • documentation: Documentation changes
  • enhancement: New Feature
  • good first issue: First contribution
  • logging: Log changes
  • refactor: Refactoring (no functional changes, no api changes)

Flags

- [ ] Breaks backward compatibility
- [ ] Requires a documentation update
- [ ] Has untestable code

---

Checklist

- [ ] Followed the guidelines in the CONTRIBUTING document
- [ ] Added prefix `[skip ci]`/`[ci skip]`/`[no ci]`/`[skip actions]`/`[actions skip]` in the PR title if necessary
- [ ] Tested and linted the code
- [ ] Commented the code
- [ ] Made corresponding changes to the documentation

Checklist for maintainer

- [ ] Use `Squash and merge`
- [ ] Double-confirm the merge message has prefix `[skip ci]`/`[ci skip]`/`[no ci]`/`[skip actions]`/`[actions skip]`
- [ ] Delete the branch after merge