chore(dx): ensure that commits with "refactor" and "perf" type cause release version change

[stalniy]

Why

Sometimes we may have changes that from end user perspective is not a feature and not a bugfix but we still want it to be released. It may be either performance improvement or some small adjustments to prepare for bigger refactoring. In this case, the commit type should be "refactor" but the issue is that by default "refactor" commits do not trigger release (version bump and excluded from changelog). This is what happened with PR #634

That's why I suggest to include "refactor" and "perf" commits to release

What

Includes "refactor" and "perf" commits to release.

Tested locally, this is an example of this change:

Changelog:
## [2.28.3](https://github.com/akash-network/console/compare/console-web/v2.28.2...console-web/v2.28.3) (2025-01-16)

### Code Refactoring
* **template:** replaces /v1/templates with /v1/templates-list ([dcc986c](https://github.com/akash-network/console/commit/dcc986cc4718fc0a4b9463d3d780a5b70f9e6cd9)), closes [#477](https://github.com/akash-network/console/issues/477)

[stalniy]

changes are done by following documentation:

1. https://github.com/conventional-changelog/conventional-changelog-config-spec/tree/master/versions/2.2.0#types
2. https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-preset-loader#preset-options