Perhaps even easier would be to go with no default config. Then create a bridge, add all ether ports to it, add wireless to it and add IP address for management access.
Where do I add the IP address for management access, and can that be a DHCP client?
Without using VLANs config goes to bridge interface
add address=<wanted IP address>/24 interface=bridge
It can be dynamic (using DHCP client) as well, but I strongly advise against it. Such setup adds complexity as you have to either find out the current IP address (from DHCP server's lease table) or you have to make sure it's static lease (DHCP server config). In addition to that, if DHCP server is not available when AP restarts, it will end up in undefined state ... which doesn't help in case you need to reconstruct your network after some major disaster.
If you plan to use VLANs, configure all VLAN stuff on switch chip and add vlan interface only for management VLAN prior to adding address (in this case address goes to vlan interface).]
Is there a special place to configure a VLAN on the switch chip, vs. RouterOS generally? If I want the flexibility of possibly running DNS and DHCP server from the CRS, would I be better off creating a management VLAN or also putting these services on the bridge interface?
It depends on particular device model, as this is switch chip specific, the actual commands will wary. The new way of doing it is unified across different HW types, but mostly means degraded performance (things are done in software rather than in switch chip). CRS switches in particular suffer as they feature many ports while their CPU is relatively slow..
In a SOHO environment using VLANs mostly means enhanced security by separating devices into different VLANs and using a firewall for connectivity between subnets. When you start to roll-out VLANs, you have to think of what support services are needed by each VLAN ... and provide those. VLANs are (in general) quite complex topic, so I suggest you do some reading. VLANs on Mikrotik are done in yet another way (almost every vendor has some peculiarities) so it does take some understanding of topic in general, thinking about how ROS implements it and decisions on how to implement it in your environment. Again, with CRS it's advisable to use external device (i.e. router) to perform inter-VLAN routing and firewalling.