The employee appraisal screen now places the button in the correct header area. This fixes an awkward visual layout so the page looks cleaner and more consistent for users.

Before 16.4, there was a single ormcache for all usage, containing 
- compile qweb templates
- t-cache
- assets_bundle related logic
- other stuff

In 16.4, this cache was split in section, mainly:

- templates: compile qweb templates + t-cache
- asserts: assets_bundle logic
- default: other stuff
...

The main issue is with t-cache, where almost anything could invalidate this cache. The t-cache key should cover this case but if not precise enough we can have inconsistencies.

In this case, the t-cache was covering t-call-assets (asset bundle)  

- Before 16.4, since all cache where invalidated, invalidating assets cache will also invalidate template cache, solving this issue
- After 16.4, this is not the case anymore. The assets-cache is invalidated, assets links in the t-cache are not valid anymore leading to 404. 

Possible solution:
- invalidate t-cache when invalidating ir_assets.
This one is sad because we will also invalidate compiled template, one of the main goal of splitting the caches.
- add assets_links to the t-cache key 
A little more complex and fragile
- invalidated t-cache in all case when invalidating other cache
This would solve all possible cache issue linked to t-cache using ormcached values.
- add t-no-cache on corresponding t-call-assets (an maybe make this automatic)
Seems like a good solution except that it will only work after updating templates 


## Proposed solution

**invalidated t-cache in all case when invalidating other cache**

Registry caches are declared this way:
```python
_REGISTRY_CACHES = {
    'default': 8192,
    'assets': 512, # arbitrary
    'templates': 1024, # arbitrary
    'routing': 1024,  # 2 entries per website
    'routing.rewrites': 8192,  # url_rewrite entries
    'templates.cached_values': 2048, # arbitrary
}
```
A structure `cache_by_prefix` was computed absed on names  (`.`)

This way, a, `templates.cached_values` was invalidated by the key `templates` and `routing.rewrites` by `routing`.
The cache_by_prefix was looking like

```python
{
    'default': ('default',),
    'assets': ('assets',),
    'templates': ('templates',),
    'routing': ('routing', 'routing.rewrites'),
}
```

This dynamicaly generated structure is replaced by an hardcoded one

```python
{
    'default': ('default', 'templates.cached_values'),
    'assets': ('assets', 'templates.cached_values'),
    'templates': ('templates', 'templates.cached_values'),
    'routing': ('routing', 'routing.rewrites', 'templates.cached_values'),
}
```

Forward-Port-Of: odoo/odoo#137816