fix(chatform): Do not interpret 祝 and 秘 as smiley.

[nickolay168]

I have updated the update_smileys.py script so that we can block and unblock smiley without loosing information. I have used the script for removing 祝 and 秘. See #613.

---

This change is 

[github-actions]

Tip

Preview URL:

[Green-Sky]

What is the status of this one?

[nickolay168]

What is the status of this one?

I have pushed more changes to fix static analysis errors. I think, it is ready now. The only failing test is related to Bazel issue.

[Green-Sky]

Looks good otherwise.

[nickolay168]

Looks good otherwise.

I have pushed the fix, but it seems, we have issues with Codacy. Is it configured through UI (It does not seems, we have .codacy.yml)? The linter has both D212 and D213 enabled, which are mutually exclusive. There is also inconsistency in Arguments processing, that results in two errors in codacy.

[Green-Sky]

I have pushed the fix, but it seems, we have issues with Codacy. Is it configured through UI (It does not seems, we have .codacy.yml)? The linter has both D212 and D213 enabled, which are mutually exclusive. There is also inconsistency in Arguments processing, that results in two errors in codacy.

I cant see "D213", but it is supposed to follow https://peps.python.org/pep-0257/#multi-line-docstrings anyway, so lets get it back to that state and then we look at the ci again.

Codacy sadly only shows the last scan for a pr.

The linter in question is Prospector btw.

[nickolay168]

Prospector

I see. In have ran prospector locally and fixed the issues with Noqa.
By default prospector -D will run both D212 and D213 checks

Multi-line docstring summary should start at the first line (D212)
Multi-line docstring summary should start at the second line (D213)

I have set # noqa D213 comments to allow PEP 257 compliant docstrings.

In some places I have suppressed D407, because if the docstring contains Args:, but rthere is no Return section, it results in failure. I.e. there is no underline under Args: section; section could not contain colon., however

Args
-----
    param: description

will result in error about undocumented parameter "param", because now args is just a section, but not the Arguments description.

@Green-Sky, I have synced the PR could you please take another look?