Optimize robotparser for long list of rules

Previously, robotparser implemented old pre-standard specification which nobody uses now. It returned the result after finding the first matching rule, which worked incorrectly in many cases (see #83368). After #138907 it follows the longest path rule.

The code can be optimized, for example by sorting rules by the path length, matching them from longest to shorter and stopping if the match is longer than the remaining paths. This can only be used for paths which do not contain metacharacters * and $.

Other optimizations can also be used, for example a trie-like structure, which could also be used for paths with metacharacters. But this will significantly complicate the code.

I am not actually sure that such optimization is necessary. In most cases the number of rules should not be too large. This is why I did not include it in the previous PR. We need to collect some data first. So I publish my code as a draft.

Linked PRs

• gh-149382

首先檢視 robotparser 的規則比對實作，以及以 gh-149382 連結的草稿工作。在選擇排序規則或類似 trie 的結構之前，收集規則清單大小與比對效能的資料；完成的條件是有證據顯示確實需要最佳化，且最長路徑行為仍然正確。