feat: Rename the card to advanced-camera-card (#1873)

Whilst the Frigate support in this card is the best among camera
engines, the name incorrectly suggests that Frigate is a requirement.
Instead, to broaden the appeal, change to more camera agnostic name.
This does not suggest any change in priority, role or support for
Frigate.

This change is likely to be bug prone, due to the size of the rename --
the code contains 1500+ references to "Frigate" most of which make sense
to rename, some which do not, all of which needed human assessment.

- Closes #1298


BREAKING CHANGE: References to `frigate-card` in all kinds of
configuration need to be updated to `advanced-camera-card`. An automated
config upgrade should take care of the majority of usecases (click `Edit
-> Upgrade -> Save`), though may not be perfect.

docs/usage/casting.md

@@ -3,7 +3,7 @@
 This card allows casting a camera stream to a Google Cast device. You can enable the cast button with:
 
 ```yaml
-type: custom:frigate-card
+type: custom:advanced-camera-card
 cameras:
   - camera_entity: camera.office
     live_provider: go2rtc
@@ -21,7 +21,7 @@ There are two different casting methods for cameras: `standard` and `dashboard`
 This is the default casting method.
 
 ```yaml
-type: custom:frigate-card
+type: custom:advanced-camera-card
 cameras:
   - camera_entity: camera.office
     live_provider: go2rtc
@@ -41,7 +41,7 @@ The main disadvantage of this method is that the stream will be played through H
 This method is powered by [Home Assistant Cast](https://cast.home-assistant.io) and requires additional configuration, but allows **low latency streaming** with go2rtc.
 
 ```yaml
-type: custom:frigate-card
+type: custom:advanced-camera-card
 cameras:
   - camera_entity: camera.office
     live_provider: go2rtc
@@ -68,7 +68,7 @@ For the example above to work, a dashboard with `dashboard-cast` URL must exist:
 
 ![image](https://github.com/user-attachments/assets/67f0e145-df05-412a-8c6d-897feb5439d2)
 
-Within that dashboard, create an `office` view and finally within that view you can place the Frigate card configured for that camera for a proper full-screen casting experience:
+Within that dashboard, create an `office` view and finally within that view you can place the Advanced Camera Card configured for that camera for a proper full-screen casting experience:
 
 ```yaml
 views:
@@ -76,7 +76,7 @@ views:
     type: panel
     path: office
     cards:
-      - type: custom:frigate-card
+      - type: custom:advanced-camera-card
         cameras:
           - camera_entity: camera.office
             live_provider: go2rtc
@@ -92,7 +92,7 @@ The `casting` profile pre-configures the card to be casted to a 16:9 screen (suc
 When casting to a Google Nest Hub, the following configuration can be used:
 
 ```yaml
-type: custom:frigate-card
+type: custom:advanced-camera-card
 cameras:
   - camera_entity: camera.office
     live_provider: go2rtc