Move circular tasks to the highmem queue

The circular tasks are not in the direct path to generate a notice. To stream execution they are better moved to the new "highmem" task

The circular tasks are among the more demanding CPU and memory usage tasks. For example, in playground the average execution time is around 9s.

• gwcelery.tasks.circulars.create_initial_circular 9.402803853037767s:
• gwcelery.tasks.circulars.create_initial_circular 9.404956129030325s:
• gwcelery.tasks.circulars.create_initial_circular 9.406347952026408s:
• gwcelery.tasks.circulars.create_initial_circular 9.407444630021928s:

time -v ligo-followup-advocate compose S241210cw

May have a large memory foot print Maximum resident set size (kbytes): 1544896= 1.544.896 that is almost 1.5 GBytes

SUBJECT: LIGO/Virgo/KAGRA S241210cw: Identification of a GW compact binary merger candidate

The LIGO Scientific Collaboration, the Virgo Collaboration, and the KAGRA
Collaboration report:
..
..
..
 [8] Ashton et al. ApJS 241, 27 (2019) doi:10.3847/1538-4365/ab06fc and
Morisaki et al. (2023) arXiv:2307.13380
	Command being timed: "ligo-followup-advocate compose S241210cw"
	User time (seconds): 6.90
	System time (seconds): 0.57
	Percent of CPU this job got: 65%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0:11.34
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 1544896
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 0
	Minor (reclaiming a frame) page faults: 46355
	Voluntary context switches: 2232
	Involuntary context switches: 218
	Swaps: 0
	File system inputs: 1136
	File system outputs: 3416
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0